resolve VS podman-nginx-socket-activation

Hi, I'm new to using podman but have been attempting to run DaVinci Resolve in a container as outlined here: https://github.com/fat-tire/resolve

Hello, I m noob on OpenSuse and Microos. I like very much it. I would like to install Davinci resolve in a container and use podman for lunch it. I would like to use: https://github.com/fat-tire/resolve . Someone already test it? I wouldn't use Nvidia driver on my microos but I would like to use it in a container? Is it possible?

Running GUI applications in containers isn't easy, there are tools that set it up for you like distrobox, but you lose out on most of the sandboxing that way. A much simpler way to isolate GUI apps is Flatpak (or snap). Discord is available on Flathub, but I couldn't find any alternative packages for Resolve. There is, however, this repo that has the containerfile to wrap the Studio version, which isn't as simple as a Flatpak, but it's a whole lot easier than figuring out the container for yourself.

Only for lack of hardware to test it on. There is an open issue if you want to try your hand at getting it to work on non-NVidia, though it will run best on some kind of dedicated GPU due to the heavy graphics operations it does.

See https://github.com/fat-tire/resolve/issues/8

FWIW, you might want to try running Resolve out of a container (Docker / Podman) : https://github.com/fat-tire/resolve

Let me also point you in the direction of https://github.com/fat-tire/resolve

https://github.com/eriksjolund/podman-nginx-socket-activatio...

I wrote an nginx socket activation example https://github.com/eriksjolund/podman-nginx-socket-activation (The example does not show nginx working as HTTP reverse proxy but I think tried that out before and it worked)

(I wrote a demo: https://github.com/eriksjolund/podman-nginx-socket-activation)

The difference is that with Podman its possible to create a systemd socket unit for the service (for example nginx.socket).

The problem when running rootless Podman with socket activation and docker.io/library/nginx is caused by the closing of file descriptor 3 in /entrypoint.sh.