Replies: 2 comments 2 replies
-
|
when you build the binary, how are you running the service. Normally, we suggest running as a socket activated service, because then the service can timeout when not being used which frees up resources, etc. You can also run the service manually like in your case, i would prob try this manually (you can even specify the socket podman should listen on). And then move to a socket activated or whatever approach. |
Beta Was this translation helpful? Give feedback.
-
|
btw, a lot of people confuse running the service privileged or unprivileged and the resulting socket. i.e. then run privileged and then try to call the unprivileged socket and are confused why it does not work. |
Beta Was this translation helpful? Give feedback.
-
|
I used this to build my last attempts: make BUILDTAGS="apparmor cni exclude_graphdriver_btrfs exclude_graphdriver_devicemapper seccomp systemd" PREFIX=/media/home/rootless/.local/But with that log-level command, I can at least inspect what is going wrong. When I built the binary before, there was no option for "podman system service". All guides used that command, but I couldn't run it. But now I see it, and it complained about nardvark. I have downloaded the binaries for the dependencies (nardvark, aardvark-dns?, and crun) and tried again, and now the process at least keeps running. I had to change the Not sure if "crun" is the correct OCI runtime to use (it says it is lightweight, which is what I would want on my Pi, but I don't know). But now the podman.service still fails. That runs the same binary, but it complains about not having access to the dependency binaries, and lists the default directories instead of the ones I have configured. Is there no way to configure the path it looks for binaries for the service also?
As I am a rootless user, and have uninstalled all systemwide podman things, I don't think this should be an issue. I simply can't run any commands with sudo. |
Beta Was this translation helpful? Give feedback.
-
|
There are still many things going wrong here, but I have "podman" up and running, I believe. When building from source, and simply setting the "PREFIX" variable to something other than /usr or /usr/local, it creates a weird file-structure (which makes sense, but the default podman will not even search these directories, only /usr/ /usr/local/, and various other static paths). Atleast when dealing with "quadlets". Anyway, but my now "services" for my podman containers can't seem to find eachother. I have a container which has both "Requires" and "After" parameters specifying my "network" service. In my systemctl logs I can see that the network service is being started and finished before my container is being started. But the container will still throw the following error:
DetailsSep 09 21:08:20 raspberrypi systemd[847]: Starting home-backend-network.service... Any ideas here? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm starting to dabble with podman as my more open alternative to docker, and also have setup a rootless user, but am running into issues. I am used to working with docker compose, and have installed podman with "apt" and generated Kubernetes specifications for use with "podman kube" from my existing Docker compose files.
This has worked fine, but I noticed I get a two year old Podman version when I install it using "apt" (version 4.3, I believe). I would like to try a newer version but can't get it working. For linux-arm64 there are only official binaries for the "remote" version (for use with a remote podman setup, I believe) but I require the full podman setup, with also the podman socket and service.
I have tried building podman from source, which does set up the socket and service, but I still have issues with the socket not being reachable.
Is there some guide on how to set up podman (version >5.0) for a rootless user on linux-arm64?
Beta Was this translation helpful? Give feedback.
All reactions