Package: podman
Version: 2.0.3+dfsg1-1
Followup-For: Bug #966093
Dear Robby and Maintainer,
to avoid the described failure in running podman *as a regular user*, it's
enough to execute the command:
$ echo 'runtime = "crun"' > ~/.config/containers/libpod.conf
afterwards, both
$ podman info
Package: podman
Version: 2.0.3+dfsg1-1
Followup-For: Bug #966093
Dear Robby and Maintainer,
while I can confirm `podman` doesn't correctly execute the `crun` runtime when
started from a regular user, after executing the following command from the
user's shell:
$ echo 'runtime = "crun"' >
Package: podman
Followup-For: Bug #966093
Dear Maintainer,
Nothing in that file is related to the issue. I have reviewed policy.json,
and swapaccount has nothing to do with runc/crun nor user namespaces.
If this is working as intended, then "Docker-compatible CLI" and "daemon-less
alternative
On Thursday, 23 July 2020 8:50:12 AM AEST rharwood wrote:
> It feels like I'm doing something wrong, but reading docs and man pages I
> am at a loss as to what.
In this case severity of this issue is unjustified.
Please check instructions in the following file
Package: podman
Version: 2.0.2+dfsg1-3
Severity: grave
Justification: renders package unusable
Dear Maintainer,
After installing podman, I get:
$ podman run -it debian:sid
Error: default OCI runtime "runc" not found: invalid argument
$
Inspecting the dependencies, I see a
5 matches
Mail list logo
