badarg,[{erl_prim_loader,check_file_result,3,[]}

[aep]

the official docker container from https://hub.docker.com/_/couchdb does not boot for me

log:

Crash dump is being written to: erl_crash.dump...done
(no error logger present) error: <0.5.0>
init terminating in do_boot ({badarg,{"init terminating in do_boot",{badarg,[{erl_prim_loader,check_file_result,3,[]},{init,patch_dir,2,[]},{init,'-patch_path/2-lc$^0/1-0-',2,[]},{init,eval_script,2,[]},{init,do_boot,3,[]}]}}
[{erl_prim_loader,check_file_result,3,[]},{init,patch_dir,2,[]},{init,-patch_path/2-lc$^0/1-0-,2,[]},{init,eval_script,2,[]},{init,do_boot,3,[]}]})

erl_crash.dump

=erl_crash_dump:0.5
Tue Jun  6 18:14:24 2023
Slogan: init terminating in do_boot ({badarg,[{erl_prim_loader,check_file_result,3,[]},{init,patch_dir,2,[]},{init,-patch_path/2-lc$^0/1-0-,2,[]},{init,e
val_script,2,[]},{init,do_boot,3,[]}]})
System version: Erlang/OTP 20 [erts-9.3.3.14] [source] [64-bit] [smp:8:8] [ds:8:8:10] [async-threads:16] [hipe] [kernel-poll:true]
Compiled: Sun Sep 26 12:40:43 2021
Taints: erl_tracer,zlib
Atoms: 3109
Calling Thread: scheduler:3
=scheduler:1
Scheduler Sleep Info Flags: SLEEPING | TSE_SLEEPING | WAITING
Scheduler Sleep Info Aux Work: 
Current Port: 
Run Queue Max Length: 0
Run Queue High Length: 0
Run Queue Normal Length: 0
Run Queue Low Length: 0
Run Queue Port Length: 0
Run Queue Flags: OUT_OF_WORK | HALFTIME_OUT_OF_WORK
Current Process: 
=scheduler:2
Scheduler Sleep Info Flags: SLEEPING | TSE

the rest of the file does not appear to reveal any more information.

are there any more useful logs?

[big-r81]

Hi,

can't help you much with docker, but which version did you use? If I look at the crash dump, there is Erlang/OTP 20, which is old and I don't know, when we release a CouchDB version with this Erlang version. Maybe check your volumes/images and try again with the latest version?

[nickva]

erl_prim_loader,check_file_result,3,[] it looks like it might not be able to perform disk I/O. Is there a chance it's a disk / volume problem.

Perhaps there was something with our docker image. But like @big-r81 mention, that's quite an old image, we also just released 3.3.3, would you be able to give that release a try? Perhaps it fixed the issue you were seeing?