Articles, notes and random thoughts on Software Development and Technology
If you follow a ‘normal’ install of docker via the install guide, you add yourself to the docker group to get permissions as a normal user to run the docker commands. If you install on Ubuntu with snap however, you still get error:
permission denied while trying to connect to the docker API at unix:///var/run/docker.sock
Per this post, you need to run this to give yourself permissions:
sudo setfacl --modify user:[your-user-id]:rw /var/run/docker.sock
docker stop [portainer-container-id]
docker run --rm -v portainer_data:/data portainer/helper-reset-password
I’m getting this error when a GitLab CI job is attempting to ‘docker compose up’ to a remote context:
$ docker --context remote compose -f docker-compose-remote-db.yml up -d --pull always
unable to get image '10.0.10.3:5000/my-image:latest': error during connect: Get "http://docker.example.com/v1.51/images/10.0.10.3:5000/adsb-dashboard:latest/json": command [ssh -l gitlab-runner -o ConnectTimeout=30 -T -- 10.0.10.3 docker system dial-stdio] has exited with exit status 255, make sure the URL is valid, and Docker 18.09 or later is installed on the remote host: stderr=Host key verification failed.
According to answers here, this could be because when the job runs for the first time the host signature has not been added to known_hosts yet. You can avoid this by:
echo "StrictHostKeyChecking no" >> ~/.ssh/config
To redeploy a service after an image has been updated:
kubectl rollout restart deployment [deployment-name]