docker-proxy remain running after unit stopped
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.1k
- Forks
- 2.2k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 43
Description
Description

Failed to start as the docker-proxy cannot closed.
Reproduce
- Error: bash: usr/bin/docker: Permission denied
- change permission: chmod 666 /usr/bin/docker
- Added SupplementaryGroups=docker
ExecStartPost=/bin/chmod 666 /var/run/docker.sock - sudo systemctl status docker
Expected behavior
No response
docker version
version:20.10.21
docker info
unable to show
Additional Info
ii docker-ce 5:20.10.213-0ubuntu-jammy amd64 Docker: the open-source application container engine
ii docker-ce-cli 5:20.10.213-0ubuntu-jammy amd64 Docker CLI: the open-source application container engine
ii docker-ce-rootless-extras 5:20.10.213-0ubuntu-jammy amd64 Rootless support for Docker.
ii docker-compose-plugin 2.12.2ubuntu-jammy amd64 Docker Compose (V2) plugin for the Docker CLI.ubuntu-jammy amd64 Docker scan cli plugin.
ii docker-scan-plugin 0.21.0
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
Start by reviewing the reported reproduction steps, the Docker 20.10.21 package details, and the sudo systemctl status docker output described in the issue. Reproduce the service stop and startup failure, then verify that docker-proxy no longer remains running after the unit stops and that Docker can start successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100