10:47 a.m.
When I pull an image, the image is 3.90GB, there is some error.
Trying to pull xxx/xxx/xxx:xxx...
Getting image source signatures
Copying blob sha256:4184ac44fb0438b126437611d02f8ef889ad8a75ca91cd75b5b328d8e08cf66d
Copying blob sha256:18fcb7509e4252365041f00982734e39ca0a44e638b8ebc18e2588405a5c7de2
Copying blob sha256:ea7643e57386e6b1e7b3524dd01d7e360b387ad640d32a7513ca263017175f87
Copying blob sha256:622a049262798701c22e70cb4e8ebff7e5dfb9c76d3dd948c49d5438ffe1e681
Copying blob sha256:d5fd17ec1767521cf97f61568096bfc9a7cd9c2d149576a7b43930c5a97062b0
Copying blob sha256:21e5db7c1fa24e99354f495e624cdc8920642b58ab65935db81bfceaf98a8a88
Copying blob sha256:ea7643e57386e6b1e7b3524dd01d7e360b387ad640d32a7513ca263017175f87
Copying blob sha256:18fcb7509e4252365041f00982734e39ca0a44e638b8ebc18e2588405a5c7de2
Copying blob sha256:d5fd17ec1767521cf97f61568096bfc9a7cd9c2d149576a7b43930c5a97062b0
Copying blob sha256:7240d5fd250b0bb7dbe6cad8d96e44e4548e895f9ca4f396275b7e0fab2dee35
Copying blob sha256:622a049262798701c22e70cb4e8ebff7e5dfb9c76d3dd948c49d5438ffe1e681
Copying blob sha256:4184ac44fb0438b126437611d02f8ef889ad8a75ca91cd75b5b328d8e08cf66d
Copying blob sha256:21e5db7c1fa24e99354f495e624cdc8920642b58ab65935db81bfceaf98a8a88
Copying blob sha256:b0b8e6c2c40a998c2efec64c1024b0ace3e6ae44f309550cf2cd0949885687c4
Copying blob sha256:7240d5fd250b0bb7dbe6cad8d96e44e4548e895f9ca4f396275b7e0fab2dee35
Copying blob sha256:b0b8e6c2c40a998c2efec64c1024b0ace3e6ae44f309550cf2cd0949885687c4
Copying blob sha256:3343333b1de32753c9c373a8396895404bc7e8653594881d8242361ecc8ed091
Copying blob sha256:3343333b1de32753c9c373a8396895404bc7e8653594881d8242361ecc8ed091
Error: writing blob: adding layer with blob
"sha256:b0b8e6c2c40a998c2efec64c1024b0ace3e6ae44f309550cf2cd0949885687c4": Error
processing tar file(signal: killed):
10:50 a.m.
On Thu, Jul 7, 2022 at 4:48 PM None via Podman <podman(a)lists.podman.io>
wrote:
When I pull an image, the image is 3.90GB, there is some error.
Trying to pull xxx/xxx/xxx:xxx...
Getting image source signatures
Copying blob
sha256:4184ac44fb0438b126437611d02f8ef889ad8a75ca91cd75b5b328d8e08cf66d
Copying blob
sha256:18fcb7509e4252365041f00982734e39ca0a44e638b8ebc18e2588405a5c7de2
Copying blob
sha256:ea7643e57386e6b1e7b3524dd01d7e360b387ad640d32a7513ca263017175f87
Copying blob
sha256:622a049262798701c22e70cb4e8ebff7e5dfb9c76d3dd948c49d5438ffe1e681
Copying blob
sha256:d5fd17ec1767521cf97f61568096bfc9a7cd9c2d149576a7b43930c5a97062b0
Copying blob
sha256:21e5db7c1fa24e99354f495e624cdc8920642b58ab65935db81bfceaf98a8a88
Copying blob
sha256:ea7643e57386e6b1e7b3524dd01d7e360b387ad640d32a7513ca263017175f87
Copying blob
sha256:18fcb7509e4252365041f00982734e39ca0a44e638b8ebc18e2588405a5c7de2
Copying blob
sha256:d5fd17ec1767521cf97f61568096bfc9a7cd9c2d149576a7b43930c5a97062b0
Copying blob
sha256:7240d5fd250b0bb7dbe6cad8d96e44e4548e895f9ca4f396275b7e0fab2dee35
Copying blob
sha256:622a049262798701c22e70cb4e8ebff7e5dfb9c76d3dd948c49d5438ffe1e681
Copying blob
sha256:4184ac44fb0438b126437611d02f8ef889ad8a75ca91cd75b5b328d8e08cf66d
Copying blob
sha256:21e5db7c1fa24e99354f495e624cdc8920642b58ab65935db81bfceaf98a8a88
Copying blob
sha256:b0b8e6c2c40a998c2efec64c1024b0ace3e6ae44f309550cf2cd0949885687c4
Copying blob
sha256:7240d5fd250b0bb7dbe6cad8d96e44e4548e895f9ca4f396275b7e0fab2dee35
Copying blob
sha256:b0b8e6c2c40a998c2efec64c1024b0ace3e6ae44f309550cf2cd0949885687c4
Copying blob
sha256:3343333b1de32753c9c373a8396895404bc7e8653594881d8242361ecc8ed091
Copying blob
sha256:3343333b1de32753c9c373a8396895404bc7e8653594881d8242361ecc8ed091
Error: writing blob: adding layer with blob
"sha256:b0b8e6c2c40a998c2efec64c1024b0ace3e6ae44f309550cf2cd0949885687c4":
Error processing tar file(signal: killed):
This smells like an out-of-memory kill. Can you share the output of
`podman info --debug`? Does your machine have enough RAM?
Kind regards,
Valentin
_______________________________________________
Podman mailing list -- podman(a)lists.podman.io
To unsubscribe send an email to podman-leave(a)lists.podman.io
11:08 a.m.
$ podman info --debug
host:
arch: amd64
buildahVersion: 1.24.1
cgroupControllers: []
cgroupManager: cgroupfs
cgroupVersion: v1
conmon:
package: Unknown
path: /home/rsync/.local/container/bin/conmon
version: 'conmon version 2.1.0, commit: unknown'
cpus: 3
distribution:
distribution: '"centos"'
version: "7"
eventLogger: file
hostname: cdesk
idMappings:
gidmap:
- container_id: 0
host_id: 3199
size: 1
- container_id: 1
host_id: 78208128
size: 35536
uidmap:
- container_id: 0
host_id: 3199
size: 1
- container_id: 1
host_id: 78208128
size: 35536
kernel: 3.10.0-1127.18.2.el7.x86_64
linkmode: dynamic
logDriver: k8s-file
memFree: 242192785408
memTotal: 404009988096
networkBackend: cni
ociRuntime:
name: runc
package: Unknown
path: /home/rsync/.local/container/sbin/runc
version: |-
runc version 1.1.0
spec: 1.0.2-dev
go: go1.16.13
libseccomp: 2.3.1
os: linux
remoteSocket:
path: /tmp/podman-run-3199/podman/podman.sock
security:
apparmorEnabled: false
capabilities:
CAP_AUDIT_WRITE,CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_MKNOD,CAP_NET_BIND_SERVICE,CAP_NET_RAW,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOT
rootless: true
seccompEnabled: true
seccompProfilePath: ""
selinuxEnabled: false
serviceIsRemote: false
slirp4netns:
executable: /home/rsync/.local/container/bin/slirp4netns
package: Unknown
version: |-
slirp4netns version 1.1.12
commit: 7a104a101aa3278a2152351a082a6df71f57c9a3
libslirp: 4.6.1.55-888d
SLIRP_CONFIG_VERSION_MAX: 4
libseccomp: 2.3.1
swapFree: 0
swapTotal: 0
uptime: 421h 49m 38.85s (Approximately 17.54 days)
plugins:
log:
- k8s-file
- none
- passthrough
network:
- bridge
- macvlan
- ipvlan
volume:
- local
registries:
search:
- docker.io
- registry.paratera.com
store:
configFile: /home/rsync/.config/containers/storage.conf
containerStore:
number: 0
paused: 0
running: 0
stopped: 0
graphDriverName: overlay
graphOptions:
overlay.mount_program:
Executable: /home/.local/container/bin/fuse-overlayfs
Package: Unknown
Version: |-
fusermount3 version: 3.10.4
fuse-overlayfs: version 1.8.2
FUSE library version 3.10.3
using FUSE kernel interface version 7.31
overlay.mountopt: nodev,fsync=0
graphRoot: /tmp/3199/share/containers/storage
graphStatus:
Backing Filesystem: tmpfs
Native Overlay Diff: "false"
Supports d_type: "true"
Using metacopy: "false"
imageCopyTmpDir: /var/tmp
imageStore:
number: 0
runRoot: /tmp/containers-user-3199/containers
volumePath: /tmp/3199/share/containers/storage/volumes
version:
APIVersion: 4.0.2
Built: 1648031621
BuiltTime: Wed Mar 23 18:33:41 2022
GitCommit: c99f9f1b6960b98158b7f5fc4e6b5ac1a10b3542
GoVersion: go1.16.13
OsArch: linux/amd64
Version: 4.0.2
1:15 p.m.
Thanks for sharing.
Please note that only Podman 1.6.4 is supported on CentOS 7. The kernel
and many other parts of the stack are just too old for newer versions of
Podman to run smoothly.
Your machine definitely has enough RAM, so I can only give some pointers.
I would first try running with Podman v1.6.4. Second, I would move the
containers storage off /tmp and onto a non-tmpfs file system. To the best
of my knowledge, systemd may clean up files in /tmp.
It would also be helpful to trace podman and see what's happening: `strace
-f podman pull`.
Kind regards,
Valentin
On Thu, Jul 7, 2022 at 5:10 PM None via Podman <podman(a)lists.podman.io>
wrote:
$ podman info --debug
host:
arch: amd64
buildahVersion: 1.24.1
cgroupControllers: []
cgroupManager: cgroupfs
cgroupVersion: v1
conmon:
package: Unknown
path: /home/rsync/.local/container/bin/conmon
version: 'conmon version 2.1.0, commit: unknown'
cpus: 3
distribution:
distribution: '"centos"'
version: "7"
eventLogger: file
hostname: cdesk
idMappings:
gidmap:
- container_id: 0
host_id: 3199
size: 1
- container_id: 1
host_id: 78208128
size: 35536
uidmap:
- container_id: 0
host_id: 3199
size: 1
- container_id: 1
host_id: 78208128
size: 35536
kernel: 3.10.0-1127.18.2.el7.x86_64
linkmode: dynamic
logDriver: k8s-file
memFree: 242192785408
memTotal: 404009988096
networkBackend: cni
ociRuntime:
name: runc
package: Unknown
path: /home/rsync/.local/container/sbin/runc
version: |-
runc version 1.1.0
spec: 1.0.2-dev
go: go1.16.13
libseccomp: 2.3.1
os: linux
remoteSocket:
path: /tmp/podman-run-3199/podman/podman.sock
security:
apparmorEnabled: false
capabilities:
CAP_AUDIT_WRITE,CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_MKNOD,CAP_NET_BIND_SERVICE,CAP_NET_RAW,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOT
rootless: true
seccompEnabled: true
seccompProfilePath: ""
selinuxEnabled: false
serviceIsRemote: false
slirp4netns:
executable: /home/rsync/.local/container/bin/slirp4netns
package: Unknown
version: |-
slirp4netns version 1.1.12
commit: 7a104a101aa3278a2152351a082a6df71f57c9a3
libslirp: 4.6.1.55-888d
SLIRP_CONFIG_VERSION_MAX: 4
libseccomp: 2.3.1
swapFree: 0
swapTotal: 0
uptime: 421h 49m 38.85s (Approximately 17.54 days)
plugins:
log:
- k8s-file
- none
- passthrough
network:
- bridge
- macvlan
- ipvlan
volume:
- local
registries:
search:
- docker.io
- registry.paratera.com
store:
configFile: /home/rsync/.config/containers/storage.conf
containerStore:
number: 0
paused: 0
running: 0
stopped: 0
graphDriverName: overlay
graphOptions:
overlay.mount_program:
Executable: /home/.local/container/bin/fuse-overlayfs
Package: Unknown
Version: |-
fusermount3 version: 3.10.4
fuse-overlayfs: version 1.8.2
FUSE library version 3.10.3
using FUSE kernel interface version 7.31
overlay.mountopt: nodev,fsync=0
graphRoot: /tmp/3199/share/containers/storage
graphStatus:
Backing Filesystem: tmpfs
Native Overlay Diff: "false"
Supports d_type: "true"
Using metacopy: "false"
imageCopyTmpDir: /var/tmp
imageStore:
number: 0
runRoot: /tmp/containers-user-3199/containers
volumePath: /tmp/3199/share/containers/storage/volumes
version:
APIVersion: 4.0.2
Built: 1648031621
BuiltTime: Wed Mar 23 18:33:41 2022
GitCommit: c99f9f1b6960b98158b7f5fc4e6b5ac1a10b3542
GoVersion: go1.16.13
OsArch: linux/amd64
Version: 4.0.2
_______________________________________________
Podman mailing list -- podman(a)lists.podman.io
To unsubscribe send an email to podman-leave(a)lists.podman.io
1212
days inactive
1212
days old
3 comments
2 participants
participants (2)
-
ugiwgh＠qq.com -
Valentin Rothberg