bigchaindb_1 | standard_init_linux.go:190: exec user process caused "no such file or directory"

[ekanath25]

I was trying to start bigchaindb and this error has occured when I did
docker-compose up bigchaindb

$ docker-compose up bigchaindb
Starting bigchaindb_tendermint_1 ...
Starting bigchaindb_mongodb_1 ...
Starting bigchaindb_tendermint_1
Starting bigchaindb_tendermint_1 ... done
Starting bigchaindb_bigchaindb_1 ...
Starting bigchaindb_bigchaindb_1 ... done
Attaching to bigchaindb_bigchaindb_1
bigchaindb_1   | standard_init_linux.go:190: exec user process caused "no such file or directory"
bigchaindb_bigchaindb_1 exited with code 1

I am using Docker Toolbox windows
How to fix this Error?

[ttmc]

I am using Docker Toolbox windows

Maybe try a more standard way of running BigchainDB Server, such as on an Linux machine or virtual machine. We don't test on windows.

[danacr]

I just did a clone of the latest git. Everything works fine in windows with docker-compose up bigchaindb, just make sure to share the right directories with docker on windows.

[CodeScriptum]

I've had the same issue on windows. it's related to line-ending auto conversion.
deleting the cloned repo and cloning again with core.autocrlf set to input solved it.

git clone https://github.com/bigchaindb/bigchaindb.git --config core.autocrlf=input

[ttmc]

Thanks @danacr and @CodeScriptum!

@danacr Our Makefile also uses (or used to use) docker-compose up bigchaindb but that was causing problems. It seems the problems can be resolved by using:

docker-compose up --no-deps mongodb tendermint bigchaindb

instead. For more background, see pull request #2341.

As for this issue, I think the above comments (by others) resolve it. Therefore I am closing this issue.

[Gxz-NGU]

I‘ve got this problem. I use windows 7, and I run the latest Docker Toolbox windows on my computer. I just put this project into E: and I use order like this:

cd /E/bigchaindb
make run

and then I've got this problem. So what's wrong with the file volume?

# although bigchaindb has tendermint and mongodb in depends_on,
# launch them first otherwise tendermint will get stuck upon sending yet another log
# due to some docker-compose issue; does not happen when containers are run as daemons
bigchaindb_mongodb_1 is up-to-date
bigchaindb_tendermint_1 is up-to-date
Starting bigchaindb_bigchaindb_1 ... error

ERROR: for bigchaindb_bigchaindb_1  Cannot start service bigchaindb: OCI runtime create failed: container_linux.go:348: starting container process cau
sed "process_linux.go:402: container init caused \"rootfs_linux.go:58: mounting \\\"/e/Developer/bigchaindb/pytest.ini\\\" to rootfs \\\"/mnt/sda1/var
/lib/docker/aufs/mnt/8a7e1f95df5db6f58fdbe1dccc0babda48adae1478e6336900c2a35ef0c6118a\\\" at \\\"/mnt/sda1/var/lib/docker/aufs/mnt/8a7e1f95df5db6f58fd
be1dccc0babda48adae1478e6336900c2a35ef0c6118a/usr/src/app/pytest.ini\\\" caused \\\"not a directory\\\"\"": unknown: Are you trying to mount a directo
ry onto a file (or vice-versa)? Check if the specified host path exists and is the expected type

ERROR: for bigchaindb  Cannot start service bigchaindb: OCI runtime create failed: container_linux.go:348: starting container process caused "process_
linux.go:402: container init caused \"rootfs_linux.go:58: mounting \\\"/e/Developer/bigchaindb/pytest.ini\\\" to rootfs \\\"/mnt/sda1/var/lib/docker/a
ufs/mnt/8a7e1f95df5db6f58fdbe1dccc0babda48adae1478e6336900c2a35ef0c6118a\\\" at \\\"/mnt/sda1/var/lib/docker/aufs/mnt/8a7e1f95df5db6f58fdbe1dccc0babda
48adae1478e6336900c2a35ef0c6118a/usr/src/app/pytest.ini\\\" caused \\\"not a directory\\\"\"": unknown: Are you trying to mount a directory onto a fil
e (or vice-versa)? Check if the specified host path exists and is the expected type
ERROR: Encountered errors while bringing up the project.
Makefile:59: recipe for target 'run' failed
make: *** [run] Error 1

When I see the docker has the volume they need, then I annotate three lines like this:
docker-compose.yml

- ./setup.py:/usr/src/app/setup.py

- ./setup.cfg:/usr/src/app/setup.cfg

- ./pytest.ini:/usr/src/app/pytest.ini

- ./tox.ini:/usr/src/app/tox.ini

then docker can work out.

[ttmc]

@Gxz-NGU Thanks for the tip!