Recreating a container lose the ip binding of exposed ports

[MarcelloPercoco]

Before you start please confirm the following.

• Yes, I've searched similar issues on GitHub.
• Yes, I've checked whether this issue is covered in the Portainer documentation or knowledge base.

Problem Description

I have some containers with exposed ports that ar binded on specific ip address of the server.

If i recreate it with the "recreate" button everything is ok, if i use "update/edit" the ip binding get lost, and i need to re-insert it before the redeploy

Expected Behavior

The ip address binding should be persist if didn't edit it explicitly

Actual Behavior

as said the ip binding get lost

Steps to Reproduce

1. select a container with exposed ports binded to specific ip
2. click) update/edit
3. redeploy the container without changing anything
4. the container ports now are exposed on every ip address

Portainer logs or screenshots

No response

Portainer version

2.20.1

Portainer Edition

Business Edition (BE/EE) with 5NF / 3NF license

Platform and Version

Docker 26.0.1

OS and Architecture

Achelinux x86_64 and Arm64

Browser

Google chrome various version

What command did you use to deploy Portainer?

docker run -d -p 127.0.0.1:9443:9443 --name portainer --restart=always --network user-bridge -v /var/run/docker.sock:/var/run/docker.sock -v /etc/portainer:/data  portainer/portainer-ee:$1

$1 obviously is desired version, portainer is bound to 127.0.0.1 because i have an haproxy in front of it.

Additional Information

No response