crun doesn't set itself as default OCI runtime for podman

[Ren Xiaolei]

I installed podman, and crun as its dependency.
When I run podman something, it says:
Error: default OCI runtime "runc" not found: invalid argument

If I add "--runtime=crun" argument to podman, it works well.

The same problem doesn't appear in Debian bullseye, because Debian use runc as podman's depencency rather than crun.

I think, crun should set itself as the default OCI runtime in post-install stage, by modifying /etc/containers/containers.conf, and everything should work well after a fresh installation.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: crun 0.14.1+dfsg-1
ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18
Uname: Linux 5.8.0-43-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
CasperMD5CheckResult: pass
Date: Fri Feb 19 07:59:55 2021
InstallationDate: Installed on 2021-02-19 (0 days ago)
InstallationMedia: Ubuntu-Server 20.10 "Groovy Gorilla" - Release amd64 (20201022)
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: crun
UpgradeStatus: No upgrade log present (probably fresh install)

[Faidon Liambotis (paravoid)]

This would be a podman (src:libpod) bug. But this has been the case as of libpod 3.0.1+dfsg1-2.