Skip to content

[WIP] Add Podman Quadlet deployment instructions to README#63

Draft
monospacedmagic wants to merge 2 commits intodeinfreu:mainfrom
monospacedmagic:patch-1
Draft

[WIP] Add Podman Quadlet deployment instructions to README#63
monospacedmagic wants to merge 2 commits intodeinfreu:mainfrom
monospacedmagic:patch-1

Conversation

@monospacedmagic
Copy link

This adds the basic rootless Podman Quadlets example from #62 to the README, if that's something you want, as a separate PR for your convenience.

Added deployment instructions using Podman Quadlets with example configuration files.
@monospacedmagic
Copy link
Author

As I mentioned in #62 (comment) I want to add to the docs in this PR as well, however that would extend the scope of this PR. I think it's worth considering to link to the docs instead then, to not spend so much README space on something that is commonly considered an alternative deployment method to Docker, as much as I want to promote it personally. What do you think? I'll set this PR to WIP for the time being, if I'm able.

@monospacedmagic monospacedmagic changed the title Add Podman Quadlet deployment instructions to README [WIP] Add Podman Quadlet deployment instructions to README Jan 18, 2026
@monospacedmagic monospacedmagic marked this pull request as draft January 18, 2026 19:21
@panromir
Copy link

panromir commented Jan 21, 2026

Hi, the Description Key goes in [Unit]

You may also want to set a Restart policy in [Service]

Furthermore I stumbled over the fact that anything in the env file that deals with Strings in the HYTALE_* Keys must not be quoted, probably an issue in hytale_config.sh but I'm not sure. Can create a new issue if confirmed not being related to podman/systemd pulling the .env file in.

After some experimentation you also need to consider, that the Server needs to be started with -ti first, to log it in.
Like this for example (adjust paths to your example):

podman run -ti --rm -v /opt/hytale/data:/home/container:rw,z -v /etc/machine-id:/etc/machine-id:ro --env-file /opt/hytale/server.env deinfreu/hytale-server:experimental

# In the console when asked to authenticate
/auth login device
# Log in
# Change Cred Store if required

The Compose Docs assume you're running in Attached mode on first run, which isn't possible with quadlets AFAIK:
Quote:
Tip: do not use -d. We need to use the terminal to authenticate the server.

@deinfreu
Copy link
Owner

Hi! Thanks a lot for your work on this, much appreciated @monospacedmagic.

I’m not going to merge this PR. The reason is that I want to keep the README.md clean. only the quick start and a small FAQ belong there.

That said, these instructions are perfect for the documentation. We can create a new page under the /technical Technical Info menu, or I can create a new Alternative Setups section, since I’d also like to include more information for TrueNAS SCALE and Unraid.

@monospacedmagic
Copy link
Author

Hi, thanks for your comments, @panromir. I'll resolve those issues in #62. Env var values pulled in by systemd do not need to be quoted, yeah. And yeah I'd need to add a section where you run the container in attached mode first, unfortunately that's still annoyingly difficult with Quadlets.

@monospacedmagic
Copy link
Author

@deinfreu I'll change this PR to add to the docs instead then. I'd say we can just do a whole technical/podman page while we're at it. I wouldn't put it into a subcategory called "Alternative setups" as that would reduce visibility, but that's just my personal preference because I want more visibility for Podman.

@deinfreu
Copy link
Owner

@monospacedmagic good thought. It is best I create a notice on the top of these instructions with a reference to the Podman installation method. This is the best way to make sure the Podman installation method has the best visibility. Also a notice with a link on the README.md and DOCKERHUB.md is good.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants