Closed hoshsadiq closed 2 years ago
Thanks for reaching out! I feel as thought this is expected behavior. The goal of this command is to clone a container, we already overwrite a lot of the namespace info. I do not think changing the network config should be done. At that point, you might as well make a new container, not clone it.
Seems reasonable. Okay, thanks!
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description I'm unable to clone a container into a pod.
Steps to reproduce the issue:
Describe the results you received: It failed with an error relating to networking. I'm assuming this is because it's trying to clone to container with its networking configuration.
Describe the results you expected: It should have cloned the container into the pod without the network configuration.
Additional information you deem important (e.g. issue happens only occasionally): N/A
Output of
podman version
:Output of
podman info
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/main/troubleshooting.md)
Yes
Additional environment details (AWS, VirtualBox, physical, etc.): Physical. Pop-OS 22.04