Was anyone able to run successfully Podman baked w/ the last build in the UDM PRO SE?

[mazzy89]

I have found out that the latest Podman baked w/ the build in this repo does not work on UDM PRO SE. I have found endless issues.

First the storage. I had to set vfs. then the containers.conf has a typo for the cgroups parameter but this was easy to spot. Now I can't run any containers. I just get

root@UDM-PRO-SE:/etc/containers# podman run docker.io/library/httpd
ERRO[0000] cannot start a container that has stopped
Error: `/usr/bin/runc start 40b6c0b453a7f8c2d0d8dbfe038a7d9a89ca62bc85f5128c2d3608e54f3bd3c3` failed: exit status 1

[mazzy89]

this has been solved. take a look here Cgroup configuration typo for Podman on UDM Pro SE

[dibun75]

Is there any easy howto guide as I cannot find any

[mazzy89]

You can download it as the artifact of the last github action build of this project. Then decompress the zip in the root and it will be installed.

[janthony6]

okay. so this is the link:
https://github.com/boostchicken-dev/udm-utilities/suites/4551796675/artifacts/122216505

what do I enter in the udmse to download from that link? and then to extract it?

[mazzy89]

Here the link from the README https://github.com/boostchicken/udm-utilities/actions download the artifacts unzip in the root of your udm pro se device and thats it

[emilvissing]

@mazzy89 but not all files necessary to have podman working are actually included in that zip, right....? storage.conf, policy.json etc.

[amomchilov]

@emilvissing Same issue here, IDK where to get policy.json from. Cross-reference: #321 (comment)

[jj358mhz]

When I unzip udmse-podman-install.zip.zip, I now see another zip called podman-install.zip in the root. Do I leave podman-install.zip as is, or do I need to unzip it as well?

[mazzy89]

Yes it's called matrioska 😂😂😂

Joking aside this is because John in the github actions of the podman relaase created as an artifact of the release a zip. So zipping a zip, you get of course as zip.

You need to unzip it as well

[StreborStrebor]

Just to be sure, If I only want to have on_boot on my UDM-SE (to run a few scripts that change MTU values), then I don't need podman, right? Or does on-boot require podman?

My aim is to keep the config as simple as possible on the UDM-SE, without unnecessary installs/configs.

[mazzy89]

on-boot is nothing than a systemd unit service that run all the sh scripts present on a location. that's it.
Podman is required in all those cases that a container is needed to be run from many different use cases like adguard, pihole, etc...

Now for your case like changing MTU values, unless you are doing that using a container, you won't need podman.

[StreborStrebor]

Thank you for the amazingly fast answer @mazzy89

[guysbrown]

I take it the case is the same if I only want to install the fan speed script (https://github.com/renedis/ubnt-auto-fan-speed).

No need for Podman, just install the boot script and the fan speed script and all it good?