Mama told me not to come.

She said, that ain’t the way to have fun.

  • 1 Post
  • 15 Comments
Joined 2 years ago
cake
Cake day: June 11th, 2023

help-circle








  • I don’t use proxmox, so I guess I don’t understand the appeal. I don’t see any reason to backup a container or a VM, I just backup configs and data. Backing up a VM makes sense if you have a bunch of customizations, but that’s pretty much the entire point of docker, you quarantine your customizations to your configs so it’s completely reproducible if you have the configs and data.


  • I don’t use proxmox, but it works absolutely fine for me on my regular Linux system, which has a firewall, some background services, etc. Could you be more specific on the issues you’re running into?

    Also, I only really expose two services on my host:

    • Caddy - handles all TLS and proxies to all other services in the internal docker network
    • Jellyfin - my crappy smart TV doesn’t seem to be able to handle Jellyfin + TLS for some reason, it causes the app to lock up

    Everything else just connects through an internal-only docker network.

    If you’re getting conflicts, I’m guessing you’ve configured things oddly, because by default, docker creates its own virtual interface to explicitly not interfere with anything else on the host.


  • You don’t have to revert 8 services, you can stop/start them independently: docker compose stop <service name>.

    This is actually how I update my services, I just stop the ones I want to update, pull, and restart them. I do them one or two at a time, mostly to mitigate issues. The same is true for pulling down new versions, my process is:

    1. edit the docker-compose file to update the image version(s) (e.g. from 1.0 -> 1.1, or 1.1 -> 2.0); I check changelog/release notes to check for any manual upgrade notices
    2. pull new images (doesn’t impact running services)
    3. docker compose up -d brings up any stopped services using new image(s)
    4. test
    5. go back to 1 until all services are done

    I do this whenever I remember, and it works pretty well.


  • I’m guessing people are largely using the wrong terminology for things that make more sense, like backing up/snapshotting config and data that containers use. Maybe they’re also backing up images (which a lot of people call “containers”), just in case it gets yanked from wherever they got it from.

    That said, yeah, someone should write a primer on how to use Docker properly and link it in the sidebar. Something like:

    1. docker-compose or podman for managing containers (a lot easier than docker run)
    2. how to use bind mounts and set permissions, as well as sharing volumes between containers (esp. useful if your TLS cert renewal is a separate container from your TLS server)
    3. docker networks - how to get containers to talk w/o exposing their ports system-wide (I only expose two ports, Caddy for TLS, and Jellyfin because my old smart TV can’t seem to handle TLS)
    4. how tags work - i.e. when to use latest, the difference between <image>:<major>.<minor>.<patch> and <image>:<major>, etc, and updating images (i.e. what happens when you “pull”)

    I’ve been using docker for years, but I’m sure the are some best practices I am missing since I’m more of a developer than a sysadmin.





  • Looks like 9? Here’s what I’m currently running:

    • actual budget
    • caddy (for TLS trunking)
    • nextcloud and collabora
    • vaultwarden (currently unused)
    • jellyfin
    • home assistant

    The rest are databases and other auxiliary stuff. I’m probably going to work on it some this holiday break, because I’d like to eventually move to microOS, and I still have a few things running outside of containers that I need to clean up (e.g. Samba).

    But yeah, like others said, it really doesn’t matter. On Linux (assuming you’re not using Docker Desktop), a container is just a process. On other systems (e.g. Windows, macOS, or Linux w/ Desktop), they run in a VM, which is a bit heavier and reserves more resources for itself. I could run 1000 containers and it really wouldn’t matter, as long as they’re pretty light.