Quadlet quickstart #92
Conversation
| [source,ini] | ||
| .... | ||
| [Unit] | ||
| Description=Podman Wolf Gamestreaming |
There was a problem hiding this comment.
This unit implies you're using a system wide podman service. This will work if you have podman.socket active when you run this unit, but it would be best if you added the dependency explicitly.
[Unit]
Description=Podman Wolf Gamestreaming
Requires=podman.service
After=podman.service
| Volume=/dev/input:/dev/input:ro | ||
| Volume=/run/udev:/run/udev:ro | ||
| Volume=/tmp/sockets:/tmp/sockets:rw | ||
| Volume=/run/podman/podman.sock:/var/run/docker.sock:ro |
There was a problem hiding this comment.
The podman.socket unit uses %t/podman/podman.sock.
The snippet here should do the same, since distros might put it in /var/run instead.
| Environment=HOST_APPS_STATE_FOLDER=/etc/wolf | ||
| Environment=GST_DEBUG=2 |
There was a problem hiding this comment.
Any reason why you manually specified those? It shouldn't be required since it's the same as the defaults
Lines 115 to 116 in e10d00b
There was a problem hiding this comment.
The original quadlet file that was posted on discord set a bunch more environment variables which I removed.
Apparently I forgot to remove the GST_DEBUG line.
The HOST_APPS_STATE_FOLDER I kept because both the docker and docker-compose blocks set that variable as well.
If you want I can remove it from all of them...
This PR adds an example quadlet file to the quickstart docs.
Quadlets are a way of describing a podman container configuration as a systemd unit.
It was adapted from what @Drakulix posted on discord, updating since renamed flags/variables and bringing the state configuration in line with the other quickstart examples.
I only added this to the Intel/AMD sections since I don't have an Nvidia GPU to test with.