Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docker running, output error #21

Open
ghost opened this issue Aug 17, 2019 · 19 comments
Open

Docker running, output error #21

ghost opened this issue Aug 17, 2019 · 19 comments

Comments

@ghost
Copy link

ghost commented Aug 17, 2019

As far as I can tell, Docker is running correctly...

sad@sad:~$ sudo docker run hello-world
Hello from Docker!
This message shows that your installation appears to be working correctly.

When trying to run prok-cheetah, I get this error:

sad@sad:~/GALES/bin$ ./run_prok_pipeline -i ../test_data/genomes/GCA_002790715.1_ASM279071v1_genomic.fna -od /tmp/demo -v cheetah -rd /dbs
Starting pipeline. If this is your first time running this pipeline there will be some latency as the necessary Docker images are downloaded. This is a one-time cost.
Running command: cwl-runner --outdir /tmp/demo /tmp/demo/prok-annotation-cheetah.cwl /tmp/demo/prok-annotation-cheetah.json
/usr/local/lib/python2.7/dist-packages/cwltool/init.py:17: CWLToolDeprecationWarning:
DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020.
Please upgrade your Python as the Python 2.7 version of cwltool won't be
maintained after that date.

""", category=CWLToolDeprecationWarning)
INFO /usr/local/bin/cwl-runner 1.0.20190815141648
INFO Resolved '/tmp/demo/prok-annotation-cheetah.cwl' to 'file:///tmp/demo/prok-annotation-cheetah.cwl'
INFO [workflow ] start
INFO [workflow ] starting step barrnap
INFO [step barrnap] start
Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get http://%2Fvar%2Frun%2Fdocker.sock/v1.38/images/json?all=1: dial unix /var/run/docker.sock: connect: permission denied
ERROR Workflow error, try again with --debug for more information:
Docker is not available for this tool, try --no-container to disable Docker, or install a user space Docker replacement like uDocker with --user-space-docker-cmd.: Command '['docker', 'images', '--no-trunc', '--all']' returned non-zero exit status 1.
ERROR: Return code 1 when running the following command: cwl-runner --outdir /tmp/demo /tmp/demo/prok-annotation-cheetah.cwl /tmp/demo/prok-annotation-cheetah.json

I looked at a similar issue, but have unable to resolve it. I am running Linux Mint, rebooted as well. If it's not Docker, it would appear to be permissions. What would I change where if that is the case?

@geraldmc
Copy link

Try running the cwl command directly:

cwl-runner --outdir /tmp/demo /tmp/demo/prok-annotation-cheetah.cwl /tmp/demo/prok-annotation-cheetah.json (or whatever the error message says the correct paths are).

@jorvis
Copy link
Owner

jorvis commented Aug 19, 2019

That's interesting, if you were able to do the test. Make sure your system as a 'docker' group and that your user is added to it, then restart your machine.

@ghost
Copy link
Author

ghost commented Aug 19, 2019 via email

@jorvis
Copy link
Owner

jorvis commented Aug 20, 2019

That error is reporting a file not missing. Does this file appear?

ls -l /tmp/demo/prok-annotation-cheetah.cwl

@ghost
Copy link
Author

ghost commented Aug 20, 2019 via email

@jorvis
Copy link
Owner

jorvis commented Aug 20, 2019

No, that's where the source copy exists. It is populated with files for YOUR run and then placed in the directory where you specify with the -od option. In your command, you said "-od /tmp/demo". So does that directory not exist on your system?

@ghost
Copy link
Author

ghost commented Aug 20, 2019 via email

@ghost
Copy link
Author

ghost commented Aug 20, 2019 via email

@jorvis
Copy link
Owner

jorvis commented Aug 20, 2019

That looks like the sort of permissions issues you get when you don't have docker completely set up. Check the output of this command and you should see 'docker' among them:

$ groups

If you don't, you need to add the unix group 'docker' and then add your user to that group, then restart.

@ghost
Copy link
Author

ghost commented Aug 20, 2019 via email

@jorvis
Copy link
Owner

jorvis commented Aug 20, 2019

OK, you did all that, restarted, and still get the same output? You didn't post anything after these modifications.

@ghost
Copy link
Author

ghost commented Aug 21, 2019 via email

@jorvis
Copy link
Owner

jorvis commented Aug 21, 2019

I'm not sure what thing is being missed but that is a classic message for when you don't have rights to run docker.

It's not the best practice, but in a pinch you can run the same command but prefix it with 'sudo' to run it with elevated privs.

@ghost
Copy link
Author

ghost commented Aug 21, 2019 via email

@jorvis
Copy link
Owner

jorvis commented Aug 21, 2019

Let's step back a bit. What happens on the command line if you do only this:

$ docker images

@ghost
Copy link
Author

ghost commented Aug 21, 2019 via email

@jorvis
Copy link
Owner

jorvis commented Aug 21, 2019

OK, so that's that. Docker itself isn't running. Really go through the installation docs for docker for your platform and see if you missed a step.

@ghost
Copy link
Author

ghost commented Aug 21, 2019 via email

@ghost
Copy link
Author

ghost commented Aug 21, 2019 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants