Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)MO
Posts
18
Comments
603
Joined
2 yr. ago

  • Definitely not necessary. If that was the case, it wouldn't live up to it's claims of being a transparent Docker replacement at all. I think you do need to use systemd if you want to go full rootless, but I haven't tried it enough to make a solid call on that.

    But yeah, with the above steps, I've moved seamlessly over to Podman for my self hosting stack and I've never looked back. It's also great because I can take literally any Docker Compose I find on the Internet and it will most likely just work.

  • You can avoid a lot of trouble by running the containers as root and using network=host

    Root yes, but you can avoid network=host most of the time pretty easily. I am still struggling with going rootless myself tbh.

  • Do you have options nvidia NVreg_PreserveVideoMemoryAllocations=1 enabled in your Nvidia kernel module options? In addition to nvidia-suspend.service, you also need nvidia-resume.service and nvidia-hibernate.service. I've never had to enable nvidia-powerd.service so that might be unnecessary for you as well.

    All of this allows your Nvidia GPU to save video memory during power management states and restore them properly on resume. Without these, you'll run into corruption issues and application crashes.

    You can consult the driver README for more info here: https://download.nvidia.com/XFree86/Linux-x86_64/545.29.06/README/powermanagement.html#PreserveAllVide719f0

  • Your issues stem from going rootless. Podman Compose creates rootless containers and that may or may not be what you want. A lot more configuration needs to be done to get rootless containers working well for persistent services that use low ports, like enabling linger for specific users or enabling low ports for non-root users.

    If you want the traditional Docker experience (which is rootful) and figure out the migration towards rootless later, I'd recommend the following:

    1. Install podman-docker. This provides a seamless Docker compatibility layer for podman, allowing you to even use regular docker commands that get translated behind the scenes into Podman.
    2. Install regular docker-compose. This will work via podman-docker and gives you the native docker compose experience.
    3. Enable podman.socket and podman-restart.service. First one socket-activates the central Podman daemon, second one restarts any podman containers with a restart-policy of always on boot.
    4. Run your docker-compose commands using sudo, so sudo docker-compose up -d etc. You can run this with sudo podman compose as well if you're allergic to hyphenation. Podman allows both rootful and rootless containers and the way you choose is by running the commands with sudo or not.

    This gets you to a very Docker-like experience and is what I am currently using to host my services. I do plan on getting familiar with rootless and systemd services and Kubernetes files, but I honestly haven't had the time to figure all that out yet.

  • I find the installation process and documentation to be absolutely batshit. ArcoLinuxL, S, B, and D? Learning phases 2, 3, 4, 6, and 7?

    It's confusing enough that you'd literally have an easier time just using the archinstall tool that's bundled on the official Arch iso.

  • Thanks! Yeah i am already using a nginx reverse proxy in a docker container to expose my other docker containers so I was thinking two reverse proxies in a row might be too inefficient. Will definitely look into nftables. Nftable rules are temporary though right? What's the correct way to automate running these rules on boot?

  • I was thinking the same thing regarding VPS and Wireguard. I use Wireguard personally to VPN into my home network for remote management, but I still haven't looked up how to make a VPS as a proxy using it. I know they can join the same network and talk with each other but what's the best way to route port 80 and 443 on the VPS to my server at home? Iptables?

  • Not OP, but I've been looking into Cloudflare tunnels on my end as well and ended up not going with them because you're forced to use their own certs so they can decrypt and see the data. I mean most likely they aren't doing anything untoward, but it's still a consideration with regards to data privacy.

  • It does have a bottom toolbar and was configured like that by default before. They must have changed the default some time ago.

    System UI is just standard Google Pixel UI and it reacts to apps signaling to it what color theme it's in. Firefox just isn't signaling it correctly. It also should be reacting normally to dark mode toggle but it doesn't because the main Fx toolbar doesn't change to light mode in the mornings. No other app has this issue.

  • I have auto dark mode during night time. In the morning, my phone will switch to light mode, but parts of the Firefox UI do not. It will be half in and out of dark mode. Bottom toolbar will be dark, but the top bar (notifications, battery, etc.) will be white text against white background. In the mornings, Youtube videos frequently wont play until I restart the app.