-
Hi all, I keep getting the following messages when trying to update my containers:
Does anyone have an idea how this could be solved? I already tried to use watchtower via the stack function in portainer and also via a separate docker-compose file (outside of portainer) - none helped. Docker version 24.0.5, build 24.0.5-0ubuntu1 |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 6 replies
-
Well, watchtower asks docker to stop a container and it just fails to do so. I don't think the way you setup watchtower matters in this situation. |
Beta Was this translation helpful? Give feedback.
-
Thank you very much @piksel for your time. I thought the same and therefore figured out that apparmor in the newest Ubuntu release might cause these problems. If anybody else ever stumbles upon this issue, this is how I solved it: sudo aa-remove-unknown The first command might be sufficient, so I wouldn't bother uninstalling apparmor, since this also uninstalls snapd. |
Beta Was this translation helpful? Give feedback.
Thank you very much @piksel for your time. I thought the same and therefore figured out that apparmor in the newest Ubuntu release might cause these problems. If anybody else ever stumbles upon this issue, this is how I solved it:
sudo aa-remove-unknown
sudo apt purge --auto-remove apparmor
sudo service docker restart
The first command might be sufficient, so I wouldn't bother uninstalling apparmor, since this also uninstalls snapd.