-
Notifications
You must be signed in to change notification settings - Fork 927
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
Container with macvlan IP uses wrong IP after recreation #1912
Comments
Seems to be fixed after 25.0.2, I had to recreate the containers else updates by watchtower kept failing. |
It happened again using docker 25.0.3, this time a different container, but again after WT recreated the container it was using the wrong static IP. See discussion here for details. Looks like the recreated container has a |
Hi, @piksel I’m sorry if you aren’t the correct person to @ - It’s my first issue in this repository and noted that you are a key/top commiter. With respect to this issue, robmry from Docker has done some deep analysis, and it appears as though the issue may require updates in WatchTower. Please see this ticket in the docker git: moby/moby#47441 (comment) As it stands Watchtower is require full manual effort after failed updates. Would really appreciate if it could be looked at. |
Would this fix watchtower not applying the mac_address? moby/moby#47474 (comment) |
Looks to be resolved after Moby 25.04+. |
Describe the bug
I get an alert from my Unifi network controller that I have a duplicate IP on my network.
The duplicate originates from my HA container, that was created to use 192.168.26 as IP, but is now using 192.168.1.3, that is a duplicate.
Today is the 2nd time I observed this, inspecting the HA container shows it is again using 192.168.1.3 instead of 192.168.1.26 as when created.
This may be related to #1906 that is related to a docker update, as I've noticed it about the same time docker was updated to v25, but could be coincidence.
Steps to reproduce
Expected behavior
Updates use the same IP.
Screenshots
Environment
Your logs
Additional context
Freshly created container:
Recreated container:
Notice the difference in network config, no
IPAddress
:The text was updated successfully, but these errors were encountered: