How do IP addresses persist on any machine reboot, and is the same public IP shared across other containers/instances outside of my control?

Hey, ThreeFold community!

Through this thread, we will be addressing a couple of interesting questions that some of our community members have asked when deploying workloads on the ThreeFold grid using the SDK.

1) How are public IP addresses allocated and how do they persist on a machine reboot?

If a container is created with a public IPv6, this IP stays constant for the lifetime of the container (even in case of node reboot). The workload will persist with the same settings until it reaches its expiration. Note that the public IP address can only be IPv6 provisioned within the container, and it remains the same throughout its lifetime.

2) Is the same public IP shared across other containers/instances outside of my control?

The container network is a private overlay network that runs on top of the farmer’s internal network (and through a Wireguard tunnel). So the outgoing / egress IPv4 address would be the same for all instances/containers. With that being said, the farmer ( or anyone else) has NO access to any of the user’s network or to your containers. All services run within the container which again is a part of private overlay network to which there are NO ingress points from the public Internet

.You can get more info right here:

If you have any specific questions about the networking architecture, you can shoot them on this thread and we will tackle them together.

Cheers everyone!

4 Likes

Great @Benjelloun.Oussama :muscle: :slightly_smiling_face:

1 Like