Error while connecting to RootlessKit API socket (Docker)
- Dominant language
- Go
- Stars
- 15.7k
- Forks
- 1.4k
- Avg merge
- 3d 8h
- Merged PRs (30d)
- 7
Description
**Describe the bug**
docker: Error response from daemon: driver failed programming external connectivity on endpoint answer (45666bb40b0f2be036d849b75acb0820b7aeba8cc583a084093c31d951eb1e65): Error starting userland proxy: error while connecting to RootlessKit API socket: stat /tmp/rootlesskit3300085503/api.sock: no such file or directory.
**To Reproduce**
Steps to reproduce the behavior:
`docker run -d -p 9080:80 -v answer-data:/data --name answer answerdev/answer:latest`
**Expected behavior**
Up and running
**Screenshots**
**Platform (please complete the following information):**
- Device: Desktop
- OS: Debian 12
- Browser .
- Version [1.2.0](https://hub.docker.com/layers/answerdev/answer/1.2.0/images/sha256-9b7fd1410df5587e56d446741760ecbd63d342c5e50587d3570e33282cf9cd77?context=explore)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the reported `docker run -d -p 9080:80 -v answer-data:/data --name answer answerdev/answer:latest` command on Debian 12 with Answer 1.2.0. Inspect the RootlessKit API socket error and the container startup result; done means the Answer container starts and runs as expected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100