attach second network to a container after is created with chatflow

[Pishoy]

is valid to add an option in chatflow for attaching an existing container to a created network in chatflow , it will be useful if someone deletes the default created network for a container ?

[grimpy]

@zaibon is this possible if you send a new reservation of the same container? Or it's not possible in zos atm?

[zaibon]

No this is not possible and not on the roadmap. Container are static things define once. If you need to modify it, cancel and re-create.

it will be useful if someone deletes the default created network for a container ?

This is indeed a problem when this happens cause the container is still "threre" but inaccessible. That's why it is important to make sure network always outlive the workloads running on top.

[grimpy]

@zaibon but I guess because of the way the bridge names on zos are made (based on the name of the network) it would always be possible to 'recreate' the network with the same information right?

[zaibon]

I don't think this works... I believe we try to see if the network would come back to live but I doubt it. It's worth trying it out though.

[grimpy]

@Pishoy I suggest you try it out and let us know