Description
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind feature
Description
Currently podman cp doesn't support for --follow-link like docker cp does.
Steps to reproduce the issue:
- podman cp --follow-link xyz.tar container:/tmp/
Describe the results you received:
Error: unknown flag: --follow-link
Describe the results you expected:
File cp command should copy target file to container.
Additional information you deem important (e.g. issue happens only occasionally):
Output of podman version:
$ podman version
Version: 3.4.7
API Version: 3.4.7
Go Version: go1.19.2
Built: Thu Jan 1 05:30:00 1970
OS/Arch: linux/arm64
Output of podman info:
$ podman info
host:
arch: arm64
buildahVersion: 1.23.1
cgroupControllers:
- cpu
- pids
cgroupManager: systemd
cgroupVersion: v2
conmon:
package: 'conmon: /usr/bin/conmon'
path: /usr/bin/conmon
version: 'conmon version 2.1.3, commit: unknown'
cpus: 4
distribution:
codename: bookworm
distribution: debian
version: unknown
eventLogger: journald
hostname: raspberrypi
idMappings:
gidmap:
- container_id: 0
host_id: 1000
size: 1
- container_id: 1
host_id: 100000
size: 65536
uidmap:
- container_id: 0
host_id: 1000
size: 1
- container_id: 1
host_id: 100000
size: 65536
kernel: 5.15.76-v8+
linkmode: dynamic
logDriver: journald
memFree: 201830400
memTotal: 3529732096
ociRuntime:
name: runc
package: 'runc: /usr/bin/runc'
path: /usr/bin/runc
version: |-
runc version 1.1.4+ds1
commit: 1.1.4+ds1-1
spec: 1.0.2-dev
go: go1.19
libseccomp: 2.5.4
os: linux
remoteSocket:
path: /run/user/1000/podman/podman.sock
security:
apparmorEnabled: false
capabilities: CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOT
rootless: true
seccompEnabled: true
seccompProfilePath: /usr/share/containers/seccomp.json
selinuxEnabled: false
serviceIsRemote: false
slirp4netns:
executable: /usr/bin/slirp4netns
package: 'slirp4netns: /usr/bin/slirp4netns'
version: |-
slirp4netns version 1.2.0
commit: 656041d45cfca7a4176f6b7eed9e4fe6c11e8383
libslirp: 4.7.0
SLIRP_CONFIG_VERSION_MAX: 4
libseccomp: 2.5.4
swapFree: 26738688
swapTotal: 104853504
uptime: 69h 57m 46.53s (Approximately 2.88 days)
plugins:
log:
- k8s-file
- none
- journald
network:
- bridge
- macvlan
volume:
- local
registries: {}
store:
configFile: /home/pi/.config/containers/storage.conf
containerStore:
number: 0
paused: 0
running: 0
stopped: 0
graphDriverName: vfs
graphOptions: {}
graphRoot: /home/pi/.local/share/containers/storage
graphStatus: {}
imageStore:
number: 19
runRoot: /run/user/1000/containers
volumePath: /home/pi/.local/share/containers/storage/volumes
version:
APIVersion: 3.4.7
Built: 0
BuiltTime: Thu Jan 1 05:30:00 1970
GitCommit: ""
GoVersion: go1.19.2
OsArch: linux/arm64
Version: 3.4.7
Package info (e.g. output of rpm -q podman or apt list podman or brew info podman):
$ apt list podman
Listing... Done
podman/testing,now 3.4.7+ds1-3+b3 arm64 [installed]
podman/testing 3.4.7+ds1-3+b3 armhf
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.):
Same behavior on other OSs