-
-
Notifications
You must be signed in to change notification settings - Fork 12.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Podman recipe requires pasta
now as well, or extra configuration to avoid needing pasta
#173699
Comments
The options for where to set the I'm not familiar with Ruby or the Homebrew recipies or I'd submit a PR myself. Changing the config should (theoretically) be pretty easy(?) until someone is nice enough to package |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
Bump |
That's really a problem. Messing with the configurations did not help. I can't even roll back to the podman v4 via brew. I also tried to install I had to uninstall podman via brew and install an old 3.4.4 version by apt. |
That's the way I suggested in containers/podman#22015: treat passt ( Which errors did you get? |
The only systems it's packaged for are the same systems that also have the latest podman available as a native package, and therefore have no reason to install podman thru brew. My recommendation is to just do what I mention at the end of the original post and add the configuration key that sets podman back to using |
Not really. For example, Debian testing and Ubuntu 24.10 ship a very recent version of the passt package, but they still ship Podman 4.9.x. What distribution are you referring to? |
For Debian and Ubuntu, released (non-testing) and LTS are what most people are using. If you're interested in up to date packages, very rarely does anyone pick a Debian-based distro. Ubuntu 24.04 (the latest LTS) doesn't have passt for example (I believe, when I was looking), nor does it have any version of podman. I'm not sure where you got info about 24.10, that doesn't release until October 2024 (year 24, month 10 = 24.10). Did you mean 23.10 maybe? |
It does: https://packages.ubuntu.com/source/noble/passt -- not the latest, but quite recent.
Why not? https://packages.ubuntu.com/source/noble/libpod -- again, not the latest, but from a few months ago.
No, I meant yet-to-be-released 24.10, see: https://packages.ubuntu.com/source/oracular/passt. |
My mistake then. I was primarily concerned with older 22.04 systems I have this deployed on and didn't look enough to find it in 24.04 apparently. Generally I'd recommend installing podman from the native package manager if there's a still supported version. Third party package managers like Homebrew don't provide much benefit in my experience when there's a recent version also available from your native distro. There's a more difficult integration that needs to happen for the third party package manager. |
I opened a PR for |
It does not work, unfortunately. After installing a new version of Podman on Ubuntu 22.04.4 LTS.
Podman info:
Reference: |
This looks unrelated, it seems to match containers/crun#1485. The problem is that while you have crun 1.16 installed, possibly via Homebrew:
Podman is using 0.17 instead:
which is installed as Ubuntu package. Can you |
brew gist-logs <formula>
link ORbrew config
ANDbrew doctor
outputVerification
brew doctor
output saysYour system is ready to brew.
and am still able to reproduce my issue.brew update
and am still able to reproduce my issue.brew doctor
and that did not fix my problem.What were you trying to do (and why)?
Installing latest
podman
and run a container with it.What happened (include all command output)?
podman
version 5.0 changed the defaultrootlessNetworkCmd
fromslirp4netns
topasta
.slirp4netns
is currently installed as part of thepodman
recipie, butpasta
is not, nor has it been packaged for Homebrew/Linuxbrew at all.The problem can be solved in the short term by setting/modifying the default
/etc/containers/containers.conf
or/usr/share/containers.conf
file to include an override for this default setting, restoring it back to the prior default that is actually provided with the podman recipe:At least until
pasta
is available from brew and included withpodman
.What did you expect to happen?
The container runs successfully without erroring out on missing tool errors.
Step-by-step reproduction instructions (by running
brew
commands)The text was updated successfully, but these errors were encountered: