influxdata / influxdata/sandbox
Got permission denied while trying to connect to the Docker daemon socket
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 490
- Forks
- 252
- PR merge metrics
- No merged PRs in 30d
Description
while running the Sanbox up facing an issue with telegraf saying:
23T16:59:05Z E! [inputs.docker] Error in plugin: 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.21/info": dial unix /var/run/docker.sock: connect: permission denied
2022-01-23T16:59:05Z E! [inputs.docker] Error in plugin: 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.21/containers/json?filters=%7B%22status%22%3A%5B%22running%22%5D%7D&limit=0": dial unix /var/run/docker.sock: connect: permission denied
i think it has something to do with https://www.influxdata.com/blog/docker-run-telegraf-as-non-root/
Contributor guide
No contributing guide indexed for this repository
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
Start with the Sandbox up path and the Telegraf Docker input configuration, then reproduce the permission-denied error against /var/run/docker.sock. Identify the configuration or setup step responsible and verify that Sandbox starts with Telegraf able to query Docker without socket permission errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, shell
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100