-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cap-add NET_ADMIN #62
Comments
That sounds like a docker bug to me. @gitdeath Can you try just updating your service manually with |
This is how I've always done it in the past and it works just fine. I suspect is has something to do with shepherd being a container without capabilities. I will run shepherd with
|
Running Shepherd with |
Well.. You could also run the |
I think I found the problem. The docker cli version in the container build doesn't meet the requirements to use
The required cli version is 20.10 |
Looks like this is due to Dockerhub environment variable setting for the ARM image. ARM = ENV DOCKER_VERSION=19.03.8 |
Ah, you are using it on ARM. Well.. That makes it a different story. The official armhf docker builds have been broken since 19.03. And as far as I heard, it seems they won't be coming back. That's why I built an image on my old arm machine manually some time ago. I guess we could use that for shepherd's armhf builds as well. |
Well my fix was to redeploy my swarm as arm64. :-) |
FYI, |
Services with cap-add NET_ADMIN do not restart with cap-add functions after being updated by Sheperd.
The text was updated successfully, but these errors were encountered: