Using podman pull command. Thanks Chris Miller Altron INC. 703-814-7647 Christopher.miller(a)altroninc.com Christopher.Miller@gd-ms.com<mailto:Christopher.Miller@gd-ms.com> From: Valentin Rothberg <vrothberg(a)redhat.com&gt; Sent: Wednesday, March 16, 2022 3:09 AM To: Miller, Christopher (NE) <Christopher.Miller(a)gd-ms.com>; Matt Heon <mheon(a)redhat.com&gt; Cc: podman(a)lists.podman.io Subject: Re: [Podman] Anyone seen Podman Exit Code 1 Error when pulling multiple images? External E-mail --- CAUTION: This email originated from outside GDMS. Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi Christopher, Thanks for reaching out. I am pulling in Matt Heon who's the export on volumes. On Tue, Mar 15, 2022 at 2:37 PM Christopher.Miller@gd-ms.com<mailto:Christopher.Miller@gd-ms.com> <Christopher.Miller@gd-ms.com<mailto:Christopher.Miller@gd-ms.com>> wrote: Running Podman v3.4.2 and when trying to pull multiple images from an on-prem with Podman we are seeing the following error message: Podman Exit Code 1 Along with the following error output: ERRO[0000] Error refreshing volume 0d947f52c097215a516f417e1df5a1fdbf1014743a656ca2d8a8f039d226ad1c: error acquiring lock 3 for volume 0d947f52c097215a516f417e1df5a1fdbf1014743a656ca2d8a8f039d226ad1c: file exists Right now if we log out of quay via CLI and then log back in, the errors stop. A quick search finds this, not sure if I'm on the correct path or not: https://docs.podman.io/en/latest/markdown/podman-container-exists.1.html If so, these containers do exist in our on-prem registry. podman-container-exists is unrelated in this case. It checks whether a container with the specified name or ID exists and will otherwise exit 1. The error above occurs when creating/running a container. It does not yet fit into the picture of being caused by multiple images being pulled in parallel. Are you doing a `podman run` or `podman pull`? Kind regards, Valetin Thanks Chris Miller Altron INC. 703-814-7647 Christopher.miller@altroninc.com<mailto:Christopher.miller@altroninc.com> Christopher.Miller@gd-ms.com<mailto:Christopher.Miller@gd-ms.com> _______________________________________________ Podman mailing list -- podman@lists.podman.io<mailto:podman@lists.podman.io> To unsubscribe send an email to podman-leave@lists.podman.io<mailto:podman-leave@lists.podman.io>

After reading thru the man page for podman system renumber, for the /usr/share/containers/containers.conf, the num_locks value is commented out (don't see a containers.conf file under /etc/containers). Looks like we'll have to uncomment that first and then run the command you have below...we'll report back. Thanks From: Matt Heon <mheon(a)redhat.com&gt; Sent: Wednesday, March 16, 2022 9:16 AM To: Miller, Christopher (NE) <Christopher.Miller(a)gd-ms.com&gt; Cc: Valentin Rothberg <vrothberg(a)redhat.com>; podman(a)lists.podman.io Subject: Re: [Podman] Re: Anyone seen Podman Exit Code 1 Error when pulling multiple images? External E-mail --- CAUTION: This email originated from outside GDMS. Do not click links or open attachments unless you recognize the sender and know the content is safe. Can you try running `podman system renumber` and see if that resolves the error message? Thanks, Matt Heon On Wed, Mar 16, 2022 at 8:30 AM Christopher.Miller@gd-ms.com<mailto:Christopher.Miller@gd-ms.com> <Christopher.Miller@gd-ms.com<mailto:Christopher.Miller@gd-ms.com>> wrote: Using podman pull command. Thanks Chris Miller Altron INC. 703-814-7647 Christopher.miller@altroninc.com<mailto:Christopher.miller@altroninc.com> Christopher.Miller@gd-ms.com<mailto:Christopher.Miller@gd-ms.com> From: Valentin Rothberg <vrothberg@redhat.com<mailto:vrothberg@redhat.com>> Sent: Wednesday, March 16, 2022 3:09 AM To: Miller, Christopher (NE) <Christopher.Miller@gd-ms.com<mailto:Christopher.Miller@gd-ms.com>>; Matt Heon <mheon@redhat.com<mailto:mheon@redhat.com>> Cc: podman@lists.podman.io<mailto:podman@lists.podman.io> Subject: Re: [Podman] Anyone seen Podman Exit Code 1 Error when pulling multiple images? External E-mail --- CAUTION: This email originated from outside GDMS. Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi Christopher, Thanks for reaching out. I am pulling in Matt Heon who's the export on volumes. On Tue, Mar 15, 2022 at 2:37 PM Christopher.Miller@gd-ms.com<mailto:Christopher.Miller@gd-ms.com> <Christopher.Miller@gd-ms.com<mailto:Christopher.Miller@gd-ms.com>> wrote: Running Podman v3.4.2 and when trying to pull multiple images from an on-prem with Podman we are seeing the following error message: Podman Exit Code 1 Along with the following error output: ERRO[0000] Error refreshing volume 0d947f52c097215a516f417e1df5a1fdbf1014743a656ca2d8a8f039d226ad1c: error acquiring lock 3 for volume 0d947f52c097215a516f417e1df5a1fdbf1014743a656ca2d8a8f039d226ad1c: file exists Right now if we log out of quay via CLI and then log back in, the errors stop. A quick search finds this, not sure if I'm on the correct path or not: https://docs.podman.io/en/latest/markdown/podman-container-exists.1.html If so, these containers do exist in our on-prem registry. podman-container-exists is unrelated in this case. It checks whether a container with the specified name or ID exists and will otherwise exit 1. The error above occurs when creating/running a container. It does not yet fit into the picture of being caused by multiple images being pulled in parallel. Are you doing a `podman run` or `podman pull`? Kind regards, Valetin Thanks Chris Miller Altron INC. 703-814-7647 Christopher.miller@altroninc.com<mailto:Christopher.miller@altroninc.com> Christopher.Miller@gd-ms.com<mailto:Christopher.Miller@gd-ms.com> _______________________________________________ Podman mailing list -- podman@lists.podman.io<mailto:podman@lists.podman.io> To unsubscribe send an email to podman-leave@lists.podman.io<mailto:podman-leave@lists.podman.io> _______________________________________________ Podman mailing list -- podman@lists.podman.io<mailto:podman@lists.podman.io> To unsubscribe send an email to podman-leave@lists.podman.io<mailto:podman-leave@lists.podman.io>

No need to uncomment the `num_locks` parameter, the default will be assumed if it is commented. The command should be safe to run at any time, though for best results it should be the only Podman process running as the user in question. Note that containers can still be running, so long as the associated `podman` process has terminated - so no running attach sessions, or long-running `podman logs` commands, or similar. Thanks, Matt Heon On Wed, Mar 16, 2022 at 9:58 AM Christopher.Miller(a)gd-ms.com < Christopher.Miller(a)gd-ms.com&gt; wrote: