kicbase runs systemd-binfmt.service and wipes out host binfmt registrations

[hpidcock]

What Happened?

On the host machine there is several binfmt registrations in /proc/sys/fs/binfmt_misc and after starting minikube using podman as the driver, those binfmt registrations are reset.

Attach the log file

Ubuntu 22.04 on AWS ec2 host:

ubuntu@ip-172-31-1-82:~$ ls /proc/sys/fs/binfmt_misc/
python3.10  qemu-aarch64  qemu-ppc64le  qemu-s390x  register  status
ubuntu@ip-172-31-1-82:~$ systemctl status systemd-binfmt.service
● systemd-binfmt.service - Set Up Additional Binary Formats
     Loaded: loaded (/lib/systemd/system/systemd-binfmt.service; static)
     Active: active (exited) since Wed 2024-03-20 00:54:43 UTC; 29min ago
       Docs: man:systemd-binfmt.service(8)
             man:binfmt.d(5)
             https://www.kernel.org/doc/html/latest/admin-guide/binfmt-misc.html
             https://www.freedesktop.org/wiki/Software/systemd/APIFileSystems
    Process: 320 ExecStart=/lib/systemd/systemd-binfmt (code=exited, status=0/SUCCESS)
   Main PID: 320 (code=exited, status=0/SUCCESS)
        CPU: 7ms
ubuntu@ip-172-31-1-82:~$ minikube start --driver=podman --container-runtime=cri-o
# wait for it to start
ubuntu@ip-172-31-1-82:~$ ls /proc/sys/fs/binfmt_misc/
python3.10  register  status

Inside the minikube privileged container on the upstream kicbase image:

root@minikube:/# systemctl status systemd-binfmt.service
● systemd-binfmt.service - Set Up Additional Binary Formats
     Loaded: loaded (/lib/systemd/system/systemd-binfmt.service; static)
     Active: active (exited) since Wed 2024-03-20 00:57:44 UTC; 30min ago
       Docs: man:systemd-binfmt.service(8)
             man:binfmt.d(5)
             https://www.kernel.org/doc/html/latest/admin-guide/binfmt-misc.html
             https://www.freedesktop.org/wiki/Software/systemd/APIFileSystems
   Main PID: 110 (code=exited, status=0/SUCCESS)
        CPU: 6ms

Mar 20 00:57:44 minikube systemd[1]: Starting Set Up Additional Binary Formats...
Mar 20 00:57:44 minikube systemd[1]: Finished Set Up Additional Binary Formats.

Operating System

Ubuntu

Driver

Podman

[afbjorklund]

The immediate issue was addressed, by removing the /usr/lib/binfmt.d/python3.10.conf

• Starting Minikube messes up binfmt config for Docker, making it unable to run cross-architecture images #17700

But it would still be a good idea to disable the service, so that it doesn't happen again...

See also: kubernetes-sigs/kind@07484ab

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.