3:50 a.m.
Thanks for reaching out.
On Mon, Aug 8, 2022 at 10:43 AM None via Podman <podman(a)lists.podman.io>
wrote:
When I pull centos:7.9.2009, it pulls successfully.
But when I pull the following image, there is errro.
$ podman --log-level debug pull myregistry/vasp:test
Copying blob d9ba75c043da skipped: already exists
Copying blob c316183b7326 skipped: already exists
Copying blob 3a0615eb7473 [>-------------------------------------] 9.6MiB
/ 250.5MiB
Copying blob d9ba75c043da skipped: already exists
Copying blob c316183b7326 skipped: already exists
Copying blob d9ba75c043da skipped: already exists
Copying blob c316183b7326 skipped: already exists
Copying blob d9ba75c043da skipped: already exists
Copying blob c316183b7326 skipped: already exists
Copying blob 3a0615eb7473 done
Copying blob a0867b88f18e done
Copying blob 6b3122725716 done
Copying blob cf4b6482cd5a done
Copying blob 5b667cbbcbe1 done
Copying blob e04fe02d5ee6 done
Copying blob 32e582c244b5 done
DEBU[0088] Error pulling candidate myregistry.com/vasp:test: writing
blob: adding layer with blob
"sha256:cf4b6482cd5adf3028b32858df192c5516f7db480601d2af3e22a7c42ad3b36a":
Error processing tar file(signal: killed):
Error: writing blob: adding layer with blob
"sha256:cf4b6482cd5adf3028b32858df192c5516f7db480601d2af3e22a7c42ad3b36a":
Error processing tar file(signal: killed):
It looks like Podman gets killed by another process. It may be due to
memory pressure.
An easy way to figure out which process is killing Podman is by using
killsnoop.
- sudo dnf install bcc-tools
- sudo /usr/share/bcc/tools/killsnoop
_______________________________________________
Podman mailing list -- podman(a)lists.podman.io
To unsubscribe send an email to podman-leave(a)lists.podman.io