8:20 a.m.
I know I didn't edit that file, however I did move storage.confg to ~/bkup/podman and
I no longer get that error.
So why? Why was I getting that error and why doing that corrected the error?
I take it .config is for individual user settings for Podman (I looked online first for
info and couldn't find anything so I'm asking here) Vs settings under
/etc/containers?
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: Brent Baude <bbaude(a)redhat.com>
Sent: Friday, February 4, 2022 9:40 PM
To: Miller, Christopher (NE) <Christopher.Miller(a)gd-ms.com>
Cc: dwalsh(a)redhat.com; podman(a)lists.podman.io
Subject: Re: [Podman] Re: Upgrade Recommendations from 1.4.2 to 3.3.1
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.
If you don't believe you have edited that file, I would be tempted to move it out to a
temporary dir and retry running podman.
On Fri, Feb 4, 2022 at 11:40 AM
Christopher.Miller@gd-ms.com<mailto:Christopher.Miller@gd-ms.com>
<Christopher.Miller@gd-ms.com<mailto:Christopher.Miller@gd-ms.com>> wrote:
Seems to have worked, just ran the dnf command (sudo dnf upgrade podman -y). I did backup
running containers to .tar.gz file before doing this.
Noticed if I issue the following command without SUDO, getting WARNING (haven't dug
into this yet):
podman --version
WARN[0000] Failed to decode the keys ["storage.options.ostree_repo"] from
"/home/millerc/.config/containers/storage.conf'.
podman version 3.4.2
Also one of my containers (Nexus) can't login to the UI either....Not sure if this is
an issue upgrading Podman or not, but want to detail my experience for others who come
behind me.
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: Daniel Walsh <dwalsh@redhat.com<mailto:dwalsh@redhat.com>>
Sent: Monday, January 31, 2022 10:47 AM
To: podman@lists.podman.io<mailto:podman@lists.podman.io>
Subject: [Podman] Re: Upgrade Recommendations from 1.4.2 to 3.3.1
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.
On 1/28/22 10:44, Christopher.Miller@gd-ms.com<mailto:Christopher.Miller@gd-ms.com>
wrote:
Hello, currently running Podman 1.4.2 on RHEL 8.1 and want to upgrade 3.3.1 so we can take
advantage of the newer features (like networking).
I am running containers currently in the 1.4.2 environment. Is there anything to think of
or do before doing an upgrade, or a best practice?
Thanks
Not that I can think of. You should be able to upgrade without much issue.
You might want to recreate your containers, if you can.
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>