I tried to get the Algorithm Reference Library Dockerfile working on my computer but had no success. These are the errors I encountered
- Dockerfile Build Errors
When using the Dockerfile as is, the command $ make docker_build PYTHON=python3 returns the following error:
cp: cannot stat './build/lib.*/*.so': No such file or directory
The command '/bin/sh -c cd /arl && $PYTHON setup.py build && $PYTHON setup.py install && cp ./build/lib.*/*.so . && cd /arl/workflows/ffiwrapped/serial && make && $PIP install mpi4py' returned a non-zero code: 1
make: *** [docker_build] Error 1
If this line is commented out it also returns:
cd: can't cd to /arl/workflows/ffiwrapped/serial
The command '/bin/sh -c cd /arl && $PYTHON setup.py build && $PYTHON setup.py install && cd /arl/workflows/ffiwrapped/serial && make && $PIP install mpi4py' returned a non-zero code: 2
make: *** [Makefile:118: docker_build] Error 2
After commenting both of these lines out, the Dockerfile will build.
- Error when running CMD /arl/boot.sh
When the container is run and docker logs is called, the result is an error message
[FATAL tini (6)] exec /arl/boot.sh failed: No such file or directory
boot.sh exists in the Dockerfile up until CMD /arl/boot.sh. I checked this by adding Docker build command RUN stat /arl/boot.sh and looking at the corresponding output when the container was building.
When running an interactive shell for the docker container, however, the file does not exist.
I couldn't find a way to fix the second problem, but virtualenv worked for me instead. Although it may not be high on your priorities, I wanted to give an account of what I tried in case Docker is something that should be fixed.
I tried to get the Algorithm Reference Library Dockerfile working on my computer but had no success. These are the errors I encountered
When using the Dockerfile as is, the command
$ make docker_build PYTHON=python3returns the following error:If this line is commented out it also returns:
After commenting both of these lines out, the Dockerfile will build.
When the container is run and docker logs is called, the result is an error message
boot.sh exists in the Dockerfile up until
CMD /arl/boot.sh. I checked this by adding Docker build commandRUN stat /arl/boot.shand looking at the corresponding output when the container was building.When running an interactive shell for the docker container, however, the file does not exist.
I couldn't find a way to fix the second problem, but virtualenv worked for me instead. Although it may not be high on your priorities, I wanted to give an account of what I tried in case Docker is something that should be fixed.