rapidsai / rapidsai/deployment
Google Compute Engine VM issues with docker
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 15
- Forks
- 41
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 6
Description
As part of testing we discover that the note we have that says
If you see a “docker socket permission denied” error while running these commands try closing and reconnecting your SSH window. This happens because your user was added to the docker group only after you signed in.
Now is a different error, and exiting the shell and getting back in doesn't work.
The tempooray solution is adding docker to the groups, then existing and getting back in.
We don't know why this is happening, we will investigate for the next release, for now we will be patching this.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the quoted Docker socket permission note in the deployment documentation and review the instructions used for Google Compute Engine VMs. Confirm the current error and temporary group workaround, then update the note to reflect the current behavior while preserving the planned investigation for the next release.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, google-cloud
- Domain
- cloud, devops, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100