Service Podman containers with Portainer App for ARM
I added the Portainer App to my AXC F 2152 controller which also runs the Node-RED App.
I would have expected to be able to see the podman containers in the Portainer App, however I'm not able to add the podman socket to the Portainer App for access to Podman containers.
It looks like
- Podman does not start it's socket on PLC start (not sure wheter this is Portainer App related or PLCnext firmware related or if this should be a manual action.
- The Portainer App does not have a volume mapping to an podman socket for managing podman containers.
I got portainer running not using the app, but on a stand alone podman container with the following commands:
A. podman system service -t 0 > /dev/null 2>&1 &
B. podman run -d -p 9443:9443 --privileged -v /run/podman/podman.sock:/var/run/docker.sock:Z docker.io/portainer/portainer-ce
Running only command A still does not enable the Portainer access to podman (issue 2). Running A & B i was able to administer podman containers via Portainer podman container.
I would like to use the apps from the store to get this behaviour instead of having to manually start services (or manually adding them to init.d) and running containers that are not from an app. How do I do this?
The Portainer App mentioned that I could get support here. If this is not the right place and I need to use the contact developer form on the App's site let me know, because then I'll repeat this there as well.
Comments
Hey,
the app uses the binary file for Portainer, not the container. Mappings are therefore unnecessary.
The last customization of the app meant that the portainer socket is started in the system. I will check this.
However, the Portainer version used is unstable with regard to podman. At that time I still had problems with the arm translation of compose, which Portainer still needed.
However, the next update is long overdue. :). I will take a look.
Thanks for your update on this matter.
I'm looking forward to an updated version :-)