Skip to content

Update for ruby 3.2#473

Merged
ctubbsii merged 2 commits intoapache:mainfrom
ctubbsii:updates
Feb 11, 2026
Merged

Update for ruby 3.2#473
ctubbsii merged 2 commits intoapache:mainfrom
ctubbsii:updates

Conversation

@ctubbsii
Copy link
Member

  • Attempt to update for ruby 3.2 again (after ASF INFRA-27632 has been completed)
  • Also update README and switch to more vendor-neutral OCI standard Containerfile with podman as the reference command instead of docker

* Attempt to update for ruby 3.2 again (after ASF INFRA-27632 has been
  completed)
* Also update README and switch to more vendor-neutral OCI standard
  Containerfile with podman as the reference command instead of docker
@DomGarguilo
Copy link
Member

Theses changes look good and I was still able to build/run via docker with

docker build -t webdev -f Containerfile .
docker run -it --rm -v "$PWD":/mnt/workdir -p 4000:4000 webdev

I am not familiar with podman. Install was easy, just installed and set

  [registries.search]
  registries = ["docker.io"]

in /etc/containers/registries.conf after getting an error with podman build

I'm fine with this switch to podman but am just curious what is the main motivation for this change?

@ctubbsii
Copy link
Member Author

I'm fine with this switch to podman but am just curious what is the main motivation for this change?

Mainly, I use podman instead of docker. But overall, I thought it was nice to move away from the vendor-specific file to a more OCI-compliant one.

I'm curious if the :Z has any impact on docker users, though, or perhaps if it has any impact on users without SELinux. It would be nice if docker behavior worked the same as podman, and if it was completely ignored on something like Ubuntu, without SELinux. Was it necessary to remove the :Z or did you just omit it as unnecessary?

@DomGarguilo
Copy link
Member

I'm fine with this switch to podman but am just curious what is the main motivation for this change?

Mainly, I use podman instead of docker. But overall, I thought it was nice to move away from the vendor-specific file to a more OCI-compliant one.

I'm curious if the :Z has any impact on docker users, though, or perhaps if it has any impact on users without SELinux. It would be nice if docker behavior worked the same as podman, and if it was completely ignored on something like Ubuntu, without SELinux. Was it necessary to remove the :Z or did you just omit it as unnecessary?

Yea it looks like running the podman command with docker runs just fine: docker run -i -t --rm -v "$(pwd)":/mnt/workdir:Z -p 4000:4000 webdev. From what I can gather, on my Ubuntu-based (Pop!_OS) machine, the :Z is just ignored. So the run command from the README seems to work interchangeably with docker and podman (at least from my machine).

Add the optional podman parameter so the same commands work with both
docker and podman
@ctubbsii ctubbsii merged commit caa7285 into apache:main Feb 11, 2026
1 check passed
@ctubbsii ctubbsii deleted the updates branch February 11, 2026 21:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments