Open kkimdev opened 2 years ago
Thanks for reaching out, @kkimdev!
The issue is related to https://github.com/containers/podman/issues/12341.
Dup #12341
Hello, @kkimdev. Is it really dup of #12341? That issue seems to be addressing progress reportting in the API. This one is about UX in Macos. Podman in macos does not report progress bars like docker or, as it appears to be the case, podman on linux. Testing with:
Version: 4.3.1
API Version: 4.3.1
Go Version: go1.18.8
Built: Wed Nov 9 17:43:58 2022
OS/Arch: darwin/arm64
Server: Podman Engine
Version: 4.3.1
API Version: 4.3.1
Go Version: go1.19.2
Built: Fri Nov 11 12:00:31 2022
OS/Arch: linux/arm64```
@srfiorini I think you're right, I believe that #12341 is a dependency, not dup.
A friendly reminder that this issue had no activity for 30 days.
Issue #12341 has been closed, seems like there are no blockers to fix this one. Can anyone confirm that podman on linux reports download progress? a comment in this thread seems to suggest it does.
@paulftw, macOS, podman-4.8.2
$ podman pull debian
Resolved "debian" as an alias (/etc/containers/registries.conf.d/000-shortnames.conf)
Trying to pull docker.io/library/debian:latest...
Getting image source signatures
Copying blob sha256:bc0734b949dcdcabe5bfdf0c8b9f44491e0fce04cb10c9c6e76282b9f6abdf01
Copying config sha256:2a033a8c63712da54b5a516f5d69d41606cfb5c4ce9aa1690ee55fc4f9babb92
Writing manifest to image destination
2a033a8c63712da54b5a516f5d69d41606cfb5c4ce9aa1690ee55fc4f9babb92
BTW the same with load
and save
as well.
If we use docker cli for podman, it shows the progress while pulling the image.
Same issue with Podman 4.9.3 on macOS (M1 processor)
Same issue with Podman 5.1.0 on macOS.
$ podman info
host:
arch: arm64
buildahVersion: 1.36.0-dev
cgroupControllers:
- cpu
- io
- memory
- pids
cgroupManager: systemd
cgroupVersion: v2
conmon:
package: conmon-2.1.10-1.fc40.aarch64
path: /usr/bin/conmon
version: 'conmon version 2.1.10, commit: '
cpuUtilization:
idlePercent: 82.92
systemPercent: 4.86
userPercent: 12.22
cpus: 5
databaseBackend: sqlite
distribution:
distribution: fedora
variant: coreos
version: "40"
eventLogger: journald
freeLocks: 2047
hostname: localhost.localdomain
idMappings:
gidmap:
- container_id: 0
host_id: 1000
size: 1
- container_id: 1
host_id: 100000
size: 1000000
uidmap:
- container_id: 0
host_id: 501
size: 1
- container_id: 1
host_id: 100000
size: 1000000
kernel: 6.8.8-300.fc40.aarch64
linkmode: dynamic
logDriver: journald
memFree: 85721088
memTotal: 2045304832
networkBackend: netavark
networkBackendInfo:
backend: netavark
dns:
package: aardvark-dns-1.10.0-1.20240506173313423293.main.51.g069ab45.fc40.aarch64
path: /usr/libexec/podman/aardvark-dns
version: aardvark-dns 1.11.0-dev
package: netavark-1.10.1-1.20240513124445753694.main.112.gd982b8b.fc40.aarch64
path: /usr/libexec/podman/netavark
version: netavark 1.11.0-dev
ociRuntime:
name: crun
package: crun-1.14.4-1.20240424212458225367.main.39.gd075e53.fc40.aarch64
path: /usr/bin/crun
version: |-
crun version UNKNOWN
commit: 320753b75c4e30085176ffc515936df286edbde2
rundir: /run/user/501/crun
spec: 1.0.0
+SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +CRIU +LIBKRUN +WASM:wasmedge +YAJL
os: linux
pasta:
executable: /usr/bin/pasta
package: passt-0^20240426.gd03c4e2-1.fc40.aarch64
version: |
pasta 0^20240426.gd03c4e2-1.fc40.aarch64-pasta
Copyright Red Hat
GNU General Public License, version 2 or later
<https://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
remoteSocket:
exists: true
path: /run/user/501/podman/podman.sock
rootlessNetworkCmd: pasta
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: true
serviceIsRemote: true
slirp4netns:
executable: /usr/bin/slirp4netns
package: slirp4netns-1.2.2-2.fc40.aarch64
version: |-
slirp4netns version 1.2.2
commit: 0ee2d87523e906518d34a6b423271e4826f71faf
libslirp: 4.7.0
SLIRP_CONFIG_VERSION_MAX: 4
libseccomp: 2.5.3
swapFree: 0
swapTotal: 0
uptime: 0h 9m 3.00s
variant: v8
plugins:
authorization: null
log:
- k8s-file
- none
- passthrough
- journald
network:
- bridge
- macvlan
- ipvlan
volume:
- local
registries:
search:
- docker.io
store:
configFile: /var/home/core/.config/containers/storage.conf
containerStore:
number: 1
paused: 0
running: 1
stopped: 0
graphDriverName: overlay
graphOptions: {}
graphRoot: /var/home/core/.local/share/containers/storage
graphRootAllocated: 106769133568
graphRootUsed: 26327990272
graphStatus:
Backing Filesystem: xfs
Native Overlay Diff: "true"
Supports d_type: "true"
Supports shifting: "false"
Supports volatile: "true"
Using metacopy: "false"
imageCopyTmpDir: /var/tmp
imageStore:
number: 1
runRoot: /run/user/501/containers
transientStore: false
volumePath: /var/home/core/.local/share/containers/storage/volumes
version:
APIVersion: 5.1.0-dev-c9808e7ed
Built: 1715558400
BuiltTime: Mon May 13 02:00:00 2024
GitCommit: ""
GoVersion: go1.22.2
Os: linux
OsArch: linux/arm64
Version: 5.1.0-dev-c9808e7ed
On Linux, running VS Code as a Flatpak and connecting to podman via podman-remote, there is no progress information displayed when layers are being pulled during the building of dev containers.
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
podman pull
doesn't show progress bars on MacOS.docker pull
shows on Mac.Steps to reproduce the issue:
podman pull docker.io/debian
Describe the results you received:
Describe the results you expected:
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version
:Output of
podman info
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Installed from Brew
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.):