Implement network configuration on container update

[schumi2004]

This is the perfect addon to manage my containers but today i noticed after updating a few that it ignores my networks configuration assigned to containers.

Many of my containers have a static IP configured like this but it gets ignored when you update them via HA/MQTT, it assigns a completly different IP from the same subnet to my containers.
Any idea why and how this happens and can it be fixed?

    networks:
      ipvlan_custom:
        ipv4_address: 10.0.0.181

networks:
  ipvlan_custom:
    name: ipvlan_custom
    ipam:
      config:
        - subnet: 10.0.0.0/24
          gateway: 10.0.0.1

[MichelFR]

Since i need to pass every parameter from the old running container restructure its data and pass it to the creation of the new container some data/config might get lost, like in this case.

Im currently working activevly on this issue and on named volume mounts since they suffer from the same issue.

Im gonna come back to this issue when i made some progress