20
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 04 Feb 2026
20 points (95.5% liked)
Linux
62340 readers
1232 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 6 years ago
MODERATORS
Yes. I put off learning it for so long and now can’t imagine self-hosting anything without it. I think all you have to do is set a static IP to the NIC from your router and then specify the IP and port in a docker-compose.yml file:
Ex:
IP-address:external-port:container-portWould LXC be more inconvenient?
Unless you're downloading a prebuilt LXC, you'd still have to do all the manual install yourself.
If you do download a prebuilt one, then you'll need to do the updating yourself, like you would a normal application, including ensuring you keep dependencies up to date and all that.
Both have their pros and cons and I use each depending on what I'm doing (and basically all of my dockers are running in their own LXC containers, which I find to be the best of both worlds).
FWIW, I don't download any prebuilt LXC anymore other than the base 'Ubuntu' or 'Debian' ones ... the ones in ProxMox that have the prebuilt apps were a pain to update for me, especially since I had no idea how they were actually installed and most of the times they didn't have package manager installations or curl installed and it was just way more trouble than it was worth.
ProxMox does now have a built in containerized docker implementation that will use an LXC and you can just provide it the docker package details, but, it's still in beta and I don't know that it's ready to be depended on yet.
Thanks. How about taking a Docker container and converting it's spec?
Sorry, not 100% sure what you mean "converting its spec"
If you mean take an existing docker and move it to a standard installation, that would depend on what all is needed. Some installations include a ton of other dockers with databases and such and you'd basically need to move them all independently and ensure the programs talk to each other properly.
For others, it's be as simple as making sure the contents of your original docker data folder is in the right place when you launch the app and you're done.
Oof, okay. Although you could probably just merge the dependencies in your LXC container? It works like this with creating appimages.
About "converting its spec": i assumed the main friction point would be the LXC tooling not knowing Dockerfiles. Forgot the name of the containers specification file (Dockerfile), since it was a while ago since i last looked into containering.
Huh, there's also "Apptainer" now? Portable and reproducible, seems interesting.
I’m assuming you mean LXC? It’s doable but without some sort of orchestration tools like Nix or Ansible, I imagine on-going maintenance or migrations would be kind of a headache.
Sweet! I'll start reading up on Docker, especially as it sounds like it has become an integral part of your self-hosting. :)
You might come across
docker runcommands in tutorials. Ignore those. Just focus on learning docker compose. With docker compose, the run command just goes into a yaml file so it’s easier to read and understand what’s going on. Don’t forget to add your user to the docker group so you aren’t having to type sudo for every command.Commands you’ll use often:
docker compose up- runs containerdocker compose up -d- runs container in headless modedocker compose down- shuts down containerdocker compose pull- pulls new imagesdocker image list- lists all imagesdocker ps- lists running containersdocker image prune -a- deletes images not being used by containers to free up spaceThanks! What a sweet little handbook for getting started! :D