On 3/22/19 11:50 AM, Robert P. J. Day wrote:
On Fri, 22 Mar 2019, Daniel Walsh wrote:
> On 3/22/19 11:32 AM, Robert P. J. Day wrote:
>> On Fri, 22 Mar 2019, Thomas S. Clayborne wrote:
>>
>>> What version of podman are you running? I see said fix was
>>> supposedly pushed to master 14 days ago, while the latest release
>>> was 17 days ago. Unless you're building from master, it's possible
>>> your version just doesn't have the fix
>> i have updates-testing enabled for my updates:
>>
>> $ podman --version
>> podman version 1.1.2
>> $
>>
>> so maybe i just have to wait another couple days.
>>
>> rday
>> _______________________________________________
>> test mailing list -- test(a)lists.fedoraproject.org
>> To unsubscribe send an email to test-leave(a)lists.fedoraproject.org
>> Fedora Code of Conduct:
https://getfedora.org/code-of-conduct.html
>> List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives:
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
> I think if you just remove
>
> .local/share/containers/storage/libpod/bolt_state.db
>
> Does it start working for you?
nope, same error. also, there's this:
$ podman ps
ERRO[0000] No subuid ranges found for user "rpjday" in /etc/subuid
$
which i see is also an issue addressed in that issues page:
https://github.com/containers/libpod/issues/2231
i have no containers or images i'm interested in keeping; perhaps
there is some value in completely cleansing my system of all of those
and starting from scratch.
rday
p.s. deleting bolt_state.db and retrying put that file back where it
was; can't tell if it matches the original file, i should have saved a
copy to compare.
Well fix your subuid ranges in /etc/subuid
Add a range of UIDs in there, this should allow you to run the containers.
In podman 1.1.2 you have to have entries in these files, to allow this
to work.