Skip to content

cri-o v1.35 fails to start on kernel v7.x #2148

@jlebon

Description

@jlebon
$ cosa run fedora-coreos-44.20260510.2.1-qemu.x86_64.qcow2
core@cosa-devsh:~$ sudo rpm-ostree install cri-o1.35 --reboot
...

core@cosa-devsh:~$ sudo sed -i '/\/usr\/libexec\/cni/d' /etc/crio/crio.conf

core@cosa-devsh:~$ sudo systemctl start crio.service
Job for crio.service failed because the control process exited with error code.
See "systemctl status crio.service" and "journalctl -xeu crio.service" for details.

core@cosa-devsh:~$ journalctl -u crio --no-pager
May 15 17:04:41 cosa-devsh systemd[1]: Starting crio.service - Container Runtime Interface for OCI (CRI-O)...
May 15 17:04:41 cosa-devsh (crio)[1481]: crio.service: Referenced but unset environment variable evaluates to an empty string: CRIO_CONFIG_OPTIONS, CRIO_METRICS_OPTIONS, CRIO_NETWORK_OPTIONS, CRIO_RUNTIME_OPTIONS, CRIO_STORAGE_OPTIONS
May 15 17:04:41 cosa-devsh crio[1481]: /usr/bin/crio: error while loading shared libraries: cannot make segment writable for relocation: Permission denied
May 15 17:04:41 cosa-devsh systemd[1]: crio.service: Main process exited, code=exited, status=127/n/a
May 15 17:04:41 cosa-devsh systemd[1]: crio.service: Failed with result 'exit-code'.
May 15 17:04:41 cosa-devsh systemd[1]: Failed to start crio.service - Container Runtime Interface for OCI (CRI-O).

So the actual error message here is:

error while loading shared libraries: cannot make segment writable for relocation: Permission denied

Reproduced on rawhide as well with 7.1 rc kernels.

Some AI investigation in alicefr/bink#52 (comment) which I think is at least partially right. Though the patches mentioned as fixing this do not in fact fix this.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions