Sorry, I just did not fix the first line when editing the test plan

** Description changed:

  [Impact]
  podman containers using the default crun backend do not work anymore with the 
6.5 HWE kernel in 22.04
  
  [Test plan]
- Needs to be finalized, but roughly:
- 
  1. Boot jammy with 6.5 HWE kernel (e.g. install linux-virtual-hwe-22.04 in a 
VM)
  2. `podman build -t systemd .` with the Dockerfile:
  FROM ubuntu:noble
  RUN apt install -U systemd -y
  CMD ["/lib/systemd/systemd"]
  3. Run it `podman run --systemd always systemd` you should not get
  Error: OCI runtime error: chmod `run/shm`: Operation not supported
  
  Optimally submitter can do end-to-end-verification on their side.
  
  [Where problems could occur]
  The patch ignores ENOTSUP for fchmodat() in one function, so at most we could 
silently hide some other issues in fchmodat() inside that function, e.g. 
AppArmor denials. But generally that is what you would want as a behavior for 
ENOTSUP...
  
  [Original bug report]
  
  The problem is very well described in https://github.com/actions/runner-
  images/issues/9425.
  
  ## COPY FROM LINK
  
  I think there might be a regression in this release of the ubuntu-22.04
  image which breaks podman.[1]
  
  The image updated the kernel from 6.2.y to 6.5.y, but podman/crun don't
  seem to be updated.
  
  Our build fails with this error link to run:[2]
  
  STEP 1/1: FROM 
ghcr.io/gardenlinux/builder:3ab2bb52bc46bb200c761369c087e9413d1ce0ac
  Trying to pull 
ghcr.io/gardenlinux/builder:3ab2bb52bc46bb200c761369c087e9413d1ce0ac...
  Getting image source signatures
  Copying blob 
sha256:041b542221cfde2f9fa4ac13f8b5804e25b23ab48ba47db2822c382a134256e1
  Copying blob 
sha256:041b542221cfde2f9fa4ac13f8b5804e25b23ab48ba47db2822c382a134256e1
  Copying config 
sha256:1eba10d0345cc6df78b7c3a6ced45da9db675d05eb20d5d286996e4f7ffb24d5
  Writing manifest to image destination
  Storing signatures
  COMMIT localhost/builder
  --> 1eba10d0345
  Successfully tagged localhost/builder:latest
  Successfully tagged 
ghcr.io/gardenlinux/builder:3ab2bb52bc46bb200c761369c087e9413d1ce0ac
  1eba10d0345cc6df78b7c3a6ced45da9db675d05eb20d5d286996e4f7ffb24d5
  Error: OCI runtime error: chmod `run/shm`: Operation not supported
  Error: Process completed with exit code 126.
  
  This is with this image version:
  
  Current runner version: '2.313.0'
  Operating System
    Ubuntu
    22.04.4
    LTS
  Runner Image
    Image: ubuntu-22.04
    Version: 20240225.1.0
    Included Software: 
https://github.com/actions/runner-images/blob/ubuntu22/20240225.1/images/ubuntu/Ubuntu2204-Readme.md
    Image Release: 
https://github.com/actions/runner-images/releases/tag/ubuntu22%2F20240225.1
  
  Trying to reproduce, it seems like I am only able to get this image
  version 20240218.1.0 where the issue does not appear.
  
  Tried to reproduce in this repo[3], but I'm not able to get this with
  image version 20240225.1.0.
  
  Is this a known issue and version 20240225.1.0 is not in use anymore?
  
  This blog post seems to suggest that the crun version is too old.[4]
  
  [1]https://github.com/actions/runner-images/releases/tag/ubuntu22%2F20240225.1
  
[2]https://github.com/gardenlinux/gardenlinux/actions/runs/8061893233/job/22020522535
  [3]https://github.com/fwilhe/turbo-lamp/blob/main/.github/workflows/podman.yml
  
[4]https://noobient.com/2023/11/15/fixing-ubuntu-containers-failing-to-start-with-systemd/

** Changed in: crun (Ubuntu Jammy)
       Status: Incomplete => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056442

Title:
  Podman (crun) regression in Ubuntu 22.04: OCI runtime error: chmod
  `run/shm`: Operation not supported

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/2056442/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to