Closed czabriskie closed 3 months ago
Running it locally works fine, but something odd happens when running it in a container. I can even edit the image so I can move into the container and run fpocket fine, but it doesn't like the mount for some reason.
thanks for reporting this. There was a change recently in how to run it in /tmp folders as this was requested by another user, it might have impacted this one. Let me see if I can add this as automated test as well.
Updated in documentation for Release 4.2
Describe the bug README example does not work for running fpocket in a docker container. The WORKDIR is incorrect and when changed to the correct WORKDIR, fpocket still doesn't produce the output expected.
To Reproduce Steps to reproduce the behavior:
docker pull fpocket/fpocket
ordocker build -t fpocket/fpocket .
docker run -v
pwd:/WORKDIR fpocket/fpocket fpocket -f data/sample/1UYD.pdb
System Properties Operating System
Docker Version
Platform
Expected behavior Data should be mounted and accessible to the container. fpocket should run on the file and output received
Output when running example
Output when modifying mount location to
/tmp
(The WORKDIR specified in theDockerfile-debian-slim
file)with no
***** POCKET HUNTING ENDS *****
as described and no output folder/file created as expected