Skip to content

podman container clone looses network info #13713

@Luap99

Description

@Luap99

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:

  1. podman network create t1

  2. podman run --network t1 --name test alpine ip a

  3. podman container clone test

  4. 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

Metadata

Metadata

Assignees

Labels

kind/bugCategorizes issue or PR as related to a bug.locked - please file new issue/PRAssist humans wanting to comment on an old issue or PR with locked comments.stale-issue

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions