portainer: No such host error when attempting to update a stack
Bug description
I’m unable to update any stack definition in portainer on v 1.17.0 running on a docker swarm with engine v17.12
Expected behavior Change the yaml for a stack and hit update, should update the stack. In this case I am change the image used.
Steps to reproduce the issue:
Steps to reproduce the behavior:
- Click on a stack
- Change any parameter (or comment out an environment variable)
- Click update the stack
- error during connect: Get https://%2Fvar%2Frun%2Fdocker.sock/v1.37/info: dial tcp: lookup /var/run/docker.sock: no such host
(code=500)
Technical details:
- Portainer version: 1.17
- Docker version (managed by Portainer): 17.12, swarm
- Platform (windows/linux): linux
- Command used to start Portainer (
docker run -p 9000:9000 portainer/portainer
): deployed as stack
version: ‘3.4’
services: portainer: image: portainer/portainer command: -H unix:///var/run/docker.sock ports: - “9000:9000” volumes: - /var/run/docker.sock:/var/run/docker.sock - vol-portainer-data:/data deploy: replicas: 1 restart_policy: delay: 10s placement: constraints: - node.role == manager
- Browser: Chrome
Additional context I’m still able to make changes to services, update containers, even use the console for a container. It’s just updating a stack that fails.
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 17 (8 by maintainers)
Commits related to this issue
- use latest compose wrapper (#1906) — committed to portainer/portainer by hookenz 2 years ago
Not sure if you are looking for general feedback, but pr1909 tag fixed it for me (same error/version/platform).