Error: starting container ... setting up Pasta: pasta failed with exit code 1 #22015
Comments
|
@paulrenn67, thanks for reporting this. Could you please try installing the passt package from Debian testing or unstable? You're running pretty much the latest upstream Podman version, but the package providing pasta(1) is the one from Debian Bookworm, and I'm fairly sure Podman can't use it to set up custom networks. For example, this commit is not included in |
|
Yes I think the old pasta version is the problem, we test with debian sid in CI so this should work fine with the lastest passt version. |
|
Pasta doesn't seem to be documented anywhere under https://podman.io/docs/installation#building-from-source pasta:
executable: ""
package: ""
version: ""Only slirp4netns is mentioned, but not the version. EDIT: Actually slirp4netns was only mentioned for |
|
Sorry guys, wasn't able to continue with this. I downgraded podman first to 4.9.3 and then to 4.1.0 (which matches another server we use) finally I was able to get the server running. Unfortunately my woes continue, not able to connect to the machine from my Mac, I have configured networks thus: I am able to ssh into Incidentally, if I don't supply the :22 port number on the image scp command, I get the following, which I thought I read was fixed a while back (I have podman 4.9.3 on my Mac): If I can't get this to work today then going to resort to old fashioned scp'ing and bash scripts :/ |
|
@afbjorklund Well updates to the docs are always welcome as you know. Feel free to report that on podman.io repo, the install instructions haven't been updated in a while. |
|
@paulrenn67 I am going to close this one then assuming it will work with the lastest pasta version. If you have other problems please make sure to file separate issues. The port thing was fixed in #21583 AFAIK and should be fixed in 5.0 and was backported to 4.9, it will in a future 4.9.4. |
By the way, there isn't really a need to downgrade anything. To install a single Debian package from testing or unstable there are a number of established ways, but given that passt has no dependencies, you could keep it quick and just |
|
As usual, the package versions vary a bit between the distribution and releases.
Well, once you find out that 1) you need |
Yes, I just maintain the Debian package, and rely on automatic Ubuntu imports which happen before every import freeze (https://wiki.ubuntu.com/DebianImportFreeze). The first Ubuntu version where this happened was 23.04.
Point 1) is a distribution matter I think -- I wouldn't know how to improve on it. On Debian, for example, Podman recommends the passt package. About 2): ...how bad can it be? |
|
It could still be worth a line in the install documentation. Even if not github (git clone https://passt.top/passt) Otherwise it will fail at runtime, since you would need one of them in order to create a rootless network.
|
Absolutely, I'm grateful you reported containers/podman.io#285 and I think that should be fixed. I'm just not sure we can improve much on those two points you raised above (outside of the documentation, I mean). |
|
They are not too bad to install from source, don't even need to venture into Cargo Hell and set up rustc and so on :-D |
|
|
|
Isn't there a way to setup an alias for package names? So that a dnf install pasta would install passt. I think for rpm setting a The podman error message could also say That said of course our install instructions need to mention it. |
|
I think it wasn't a requirement previously, because you could (in theory) run everything with EDIT: Like: you could run without networking and with a single user on a slow storage, but it wouldn't be fun So it is "recommended" to install the dependencies as well (that would be the |
|
The main issue here is the version breakage, which means it will need to get dumped into Similar to the |
And this is what we discussed and decided that it should be a requires because by default podman run wouldn't work.
What breakage? We need a recent passt and that is to be expected. I do not see anything wrong with that or what we would gain by moving it into a different location (and yes we already check libexec/podman for pasta). |
|
Just saying that it would be nice if it was possible to check the "API" versions of the dependencies, that's all. Then again passt doesn't even seem to have any versions. The tags seems to be mostly based on date/commit. |
But the issue at hand was really an issue in pasta -- not an intended behaviour or an API change. We're being really careful with functional changes and so far I think we avoided to introduce any (deliberate) breakage.
Those are the actual versions: passt doesn't use semantic versioning. You have the ISO-8601 date so you know (approximately) when the release was made, and 7 digits of git SHA you can use to quickly navigate the code from a given release. I personally find that more meaningful than "passt 3.11" or suchlike. |
I have to look into this. On Debian there are virtual packages (https://www.debian.org/doc/debian-policy/ch-relationships.html#s-virtual), but they're mostly used to represent possible alternatives providing similar functionality, and especially satisfying a dependency. On RPM-based distributions, |
|
What's the solution for installing podman in Previously I could install Podman 4.x on Ubuntu without any issues. |
Can't you install pasta using the official Ubuntu package? |
|
It doesn't look like I could:
|
I guess your Ubuntu version is too old to contain any version of passt? In that case, I guess you can install a single package from a newer Ubuntu version. |
|
I think getting recent packages of the Podman ecosystem is generally difficult since there aren't any stable and new ones any more as far as I know. And I think it's even more difficult for pasta. Apart from that mixing package sources might lead to further problems as well. But I don't have a strong Podman background so I might misunderstand the constraints here. 😉 PS: thank you for your quick answer by the way! I really appreciate this! |
It shouldn't be, it's a much smaller/simpler beast with fewer interactions, and zero dependencies other than a standard C library. There are updated packages for many distributions.
Sure, it would be nice to have a Homebrew package as well, but I already maintain passt/pasta packages for a few distributions, including the one for Debian (which periodically gets synchronised with Ubuntu), so I guess you would have to find somebody interested in maintaining that. I hope you have more luck on Homebrew/homebrew-core#173714.
I don't think that Homebrew ships every single dependency of Podman. For example, I'm fairly sure you can't run Podman on Linux without Bash, but Bash isn't taken care of in Podman's Homebrew formula. Some things are just system dependencies (pasta could be one of them as well) and maybe there is a way to list them as such ( |
Issue Description
Hi,
I'm new to Podman, and trying to setup a new server with only a basic Debian 12 install. I spent a while configuring the server, trying to load all the dependencies needed for Podman, upgraded Go, and Podman should be the latest:
I'm attempting to install a rootless user, and I'm finally at a place where I can actually create and attempt to start a pod.
However, Pasta networking fails at startup, here is output from
podman pod start psp-pod --log-level=debugChecking the rootless-netns file, it is empty:
Not sure how to continue further, does anybody have any clues? Happy to assist and provide any further information if required!
Thanks in advance,
Paul
Steps to reproduce the issue
Steps to reproduce the issue
Describe the results you received
Error: starting container 2ba3568f71cfd3779ebfbc53ccfeb084e539605c2f3299ef4630f9ba8a743964: setting up Pasta: pasta failed with exit code 1:
Couldn't open network namespace /run/user/1000/containers/networks/rootless-netns/rootless-netns
Describe the results you expected
Pod should start cleanly
podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
Additional environment details
Additional information
Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting
The text was updated successfully, but these errors were encountered: