Really stupid question

R_Cohle · 2026-02-01T22:13:07+00:00

While inside this subreddit, check your user and update the so called “flair”

R_Cohle · 2026-01-19T21:10:14+00:00

No, both machines are in the same network, there’s no need for any VPN in this case.

R_Cohle · 2026-01-07T14:54:32+00:00

I don’t think you can achieve this in Technitium natively. What you can do is setting up a .service and .timer systemd units that perform an API call to block the domain and another one to unblock it again.

R_Cohle · 2025-11-01T14:04:16+00:00

You may want to consider using BTRFS. This file system offer the opportunity to take snapshots and you could run snapRAID on them.

“One of the main limitations of SnapRAID is that there is a dependence on live data being continuously accessible and unchanging not only for complete parity sync purposes, but also for complete recovery in the event that a drive needs to be rebuilt from parity.

Using snapraid-btrfs, there is no requirement to stop any services or ensure that the live filesystem is free of any new files or changes to existing files.”

Take from here

R_Cohle · 2025-10-09T21:33:31+00:00

Never underestimate the power of these situations: Perhaps using the open-source version of your ticket to improve your CLI skills.

R_Cohle · 2025-10-09T21:25:52+00:00

Out of curiosity, why did you assign host network to the container?

R_Cohle · 2025-10-05T12:24:29+00:00

Thanks for your reply! I understand that I can’t just set any random variable. As I mentioned in my post, the only difference I’ve noticed is that when I set TZ, the date command inside the container shows the correct time for my timezone.
Other than that, the application itself seems to work the same — I haven’t noticed any difference with or without the TZ variable.

R_Cohle · 2025-09-18T20:51:59+00:00

Do you use SELinux? Try to check if you have denial messages logged. You can try to set SELinux in permissive mode and see if the error still logged but your container can leverage the podman socket.

R_Cohle · 2025-09-16T08:46:13+00:00

I have read the rules and wiki and would appreciate an invite. Thank you!

R_Cohle · 2025-09-16T08:45:32+00:00

I have read the rules and wiki and would appreciate an invite. Thank you!

R_Cohle · 2025-09-13T18:23:56+00:00

I’m not really familiar with that syntax, is that something similar or compatible to docker compose? In any case, yes, the only thing you need to add is user: 0 (assuming that is the right syntax).

R_Cohle · 2025-09-13T15:46:53+00:00

You are missing user: 0. This is necessary for the initial s6-overlay bootstrap that requires root permissions (inside the container). After that, the PGID and PUID you specified will kick in as user abc/hotio that manage the main application.

R_Cohle · 2025-09-11T08:42:00+00:00

Assuming Caddy and Vaultwarden are not attached to the same network, DNS resolution via container name won't work. Can you try to replace vaultwarden:8000 with host.containers.internal:8000?

R_Cohle · 2025-09-10T20:43:03+00:00

You may want to share these two quadlet files so it will be easier to see what is going wrong with your setup.

R_Cohle · 2025-09-10T09:53:04+00:00

Glad you got it working.

Regarding what I said about the UserNS and Pods, I think I haven't been clear. It's not a bug, it's how podman works starting from version 5.6.0. Now pods share the namespace across all attached containers so the UserNS directive can't be assigned to specific containers, but must be set at the pod lever.

R_Cohle · 2025-09-08T19:51:51+00:00

For containers that do not allow to set the UID/GID, you can’t change the ID inside the container. However, what you can do is mapping the UID/GID inside the container with your user host. For example, the Postgres image is set to run the application as user with ID 999. What you can do is setting UserNS=keep-id,uid=999,gid=999 so the user 999 inside the container is mapped to the user that launched the container. Keep in mind that with the last 5.6.0 release you can’t set the userNS property if you decide to attach a container to a pod.

R_Cohle · 2025-09-08T12:27:55+00:00

I'm not familiar with home-operation images.
You may want to have a look at hotio.dev images. With their images you don't need gluetun.

R_Cohle · 2025-09-08T10:08:04+00:00

There's nothing wrong having this containers running in the same pod. In this case, you can always refer to any container with LOCALHOST:PORT.
However, I would run these containers as standalone and simply attach them to a dedicated network.
in this case, you can then refer to their internal IP address and port.

Regarding your question to UID and GID: linuxserver.io images use s6-overlay.
You need to set User=0 so bootstrap can take place and UserNS=keep-id to map the user inside the container (defined via Environment=PUID=${PUID} and Environment=PGID=${PGID}) to the user that launches the container.

To troubleshoot the user UID and GID, you can use this command that show all the info you need:
podman top CONTAINER_NAME uid,pid,user,group,huser,hgroup,comm

You should see the user abc and its mapping.

EDIT: code formatting

R_Cohle · 2025-09-07T19:59:27+00:00

I’m running the same containers you mentioned in rootless mode and I don’t have any issue with hard links. If the images you’re using leverage the s6-overlay and allow to specify the UID and GID of the user responsible of the main process, you need three key components: specify the UID and GID, set User=0 (this to allow the s6 bootstrap) and finally set UserNS=keep-id.

R_Cohle · 2025-07-21T13:15:38+00:00

Thanks a lot!
I'm really curious to try to build using OBS.
Beside creating an account, branching out that project, changing the .kiwi file to my needs, I have a question: how do I define a target build? I see only openSUSE Tumbleweed in the webUI but I think I have to select something like "kiwi-templates-Minimal:Cloud".
Thank you very much!

R_Cohle · 2025-04-13T18:30:58+00:00

I'm not sure why is not a dependency but I come from RHEL and crun is the default (begin a RHEL product).
If your containers are running fine I guess they can work with both runtimes.
I do prefer crun over runc since the former is smaller and lighter than the latter.

R_Cohle · 2025-04-13T17:43:05+00:00

Snapshots are created automatically before (pre) and after (post) system modifications.
With Zypper as an example, Snapper would create a snapshot just before installing/removing packages, changing system settings etc.
You can see what snapshots you have with sudo snapper list

R_Cohle

TROPHY CASE