-
Notifications
You must be signed in to change notification settings - Fork 3k
Description
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Podman clone looses network information for the container. All networks are removed from the container and is only keeps the default one.
Steps to reproduce the issue:
-
podman network create t1 -
podman run --network t1 --name test alpine ip a -
podman container clone test -
podman start --attach test-clone
Describe the results you received:
The container is attached to the default network. All settings are removed.
Describe the results you expected:
The cloned container should be attached to the same network.
Additional information you deem important (e.g. issue happens only occasionally):
Podman stores the network information inside an extra db bucket and not the container config. I guess container clone must read from the there and not the settings in the container config.
Output of podman version:
Client: Podman Engine
Version: 4.0.0-dev
API Version: 4.0.0-dev
Go Version: go1.16.15
Git Commit: ff8834f0232f128b781ec23d66a5676da0670847
Built: Wed Mar 30 14:16:36 2022
OS/Arch: linux/amd64