[Bug] Updating containers with macvlan networking breaks static IP configuration

[sampl3x]

What’s the bug?

[BUG] Updating a container through Tugtainer causes macvlan network configuration and static container IPs to be lost.

Description

When a container that uses a macvlan network with a static IPv4 address is updated via Tugtainer, the container is recreated without the original network settings.

After the update:
• The container is no longer attached to the macvlan network
• The container receives a random IP (e.g. 192.168.0.2) or is moved to the default bridge network
• The configured ipv4_address: in docker-compose.yml is ignored
• The external macvlan network (lan) is not reapplied

This behavior does not occur when updating the container normally using the docker-compose.yml:

docker compose pull
docker compose up -d

So the issue appears to be related to how Tugtainer handles the container recreation process.

Expected behaviour

Tugtainer should: Recreate containers with their original macvlan configuration of the docker container

To reproduce

1.	Create a container using docker-compose with a macvlan network:

services:
  yadnsb:
    image: ghcr.io/example
    container_name: yadnsb
    networks:
      lan:
        ipv4_address: 192.168.0.201
networks:
  lan:
    external: true
    name: lan

2.	Confirm the container has the correct IP:

docker exec -it yadnsb ip a
# → 192.168.0.201

3.	Update the container using Tugtainer’s Update function
4.	Check the network again:

docker exec -it yadnsb ip a

Result:
Container now has an unexpected IP (e.g. 192.168.0.2) and no longer sits on the macvlan network.

Platform

Terramaster NAS TOS6

Versions

Tugtainer Docker image: quenary/tugtainer:latest v1.7.0

Relevant log output

Extra

No response

[goppinath]

Yes, I can confirm this. I would really appreciate it if this issue could be resolved in the near future.

[codinv]

I have the same problem

[snakwu]

@Quenary I have the same problem. When will it be fixed? Thank you.

[thekoma]

It will be fixed when someone does a PR with a fix.
Either the owner of the repo or someone that is willing to spend his precious time in a free project.
Maybe you?

[Quenary]

Hi. Thanks for the issue. I'll take a look when I have time. For now, you can use check only for such containers.

[snakwu]

Yes, currently, containers using MACVLAN can only perform automatic checks for new images—you’ll need to update them manually when a new image is available.
Additionally, it’s a pity that Tugtainer itself cannot update automatically.

Thank you again for developing this project—thank you!

[Quenary]

gabrieldemarmiesse/python-on-whales#699