On 4/6/21 09:19, lejeczek via Podman wrote:
On 05/04/2021 22:02, Daniel Walsh wrote:
> On 4/4/21 12:03, lejeczek via Podman wrote:
>> Hi guys.
>>
>> My podman created a network, just with:
>>
>> -> $ podman network create
>> /home/podmania/.config/cni/net.d/cni-podman0.conflist
>>
>> then created a pod:
>>
>> -> $ podman pod create --network cni-podman0 --hostname some ---name
>> some
>>
>> then tried to create a container:
>>
>> -> $ podman run -it --pod=some --name some-nettols
>> docker.io/pmietlicki/nettools
>> ERRO[0000] error starting some container dependencies
>> ERRO[0000] "container_linux.go:370: starting container process
>> caused: unknown capability \"CAP_PERFMON\": OCI runtime error"
>> Error: error starting some containers: internal libpod error
>>
>> Is that a limitation by design? I see that while run "rootless" and
>> am on CentOS Stream with:
>>
>> podman-3.1.0-0.13.module_el8.5.0+733+9bb5dffa.x86_64
>> 4.18.0-294.el8.x86_64
>>
>> many thanks, L.
>> _______________________________________________
>> Podman mailing list -- podman(a)lists.podman.io
>> To unsubscribe send an email to podman-leave(a)lists.podman.io
>
> There is an issue with crun version here. I don't believe that there
> is an update of libcap available for centos stream, and crun needs it.
> _______________________________________________
> Podman mailing list -- podman(a)lists.podman.io
> To unsubscribe send an email to podman-leave(a)lists.podman.io
Thank you.
Would that qualify as a 'bug report' which should go into Redhat's
Bugzilla under "Centos"?
_______________________________________________
Podman mailing list -- podman(a)lists.podman.io
To unsubscribe send an email to podman-leave(a)lists.podman.io
Yes.