this post was submitted on 07 Feb 2025
971 points (100.0% liked)

linuxmemes

24211 readers
1143 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
    • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn, no politics, no trolling or ragebaiting.
    • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
    • 5. πŸ‡¬πŸ‡§ Language/язык/Sprache
  • This is primarily an English-speaking community. πŸ‡¬πŸ‡§πŸ‡¦πŸ‡ΊπŸ‡ΊπŸ‡Έ
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
    • 6. (NEW!) Regarding public figuresWe all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
    •  

    Please report posts and comments that break these rules!

    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.

    founded 2 years ago
    MODERATORS
    poopsmith@lemmy.world
    zephyr@lemmy.world
    rtxn@lemmy.world
    971
    My Self Hosting Journey (feddit.nu)
    submitted 1 month ago by hanke@feddit.nu to c/linuxmemes@lemmy.world
    190 comments fedilink hide all child comments
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] targetx@programming.dev 2 points 1 month ago (1 children)

    Do you run Docker in a VM or on the host node? I'm running a lot of LXC at home on Proxmox but sometimes it'd be nice to run Docker stuff easily as well.

    [–] wildbus8979@sh.itjust.works 1 points 1 month ago (2 children)

    Just create an LXC container to run your dockers, all you have to do is make sure you run the LXC as privileged and enable nesting.

    [–] Dran_Arcana@lemmy.world 3 points 1 month ago (1 children)

    There are security performance and capability concerns with that approach, apparmor on the first layer lxc probably being the most annoying.

    If you want to isolate your docker sandbox from your main host, you should use a vm not a container.

    [–] wildbus8979@sh.itjust.works 1 points 1 month ago* (last edited 1 month ago) (1 children)

    OP's already running LXC on the host, so... Namespaces are namespaces...

    I don't see what performance issues there would be with that.

    [–] Dran_Arcana@lemmy.world 1 points 1 month ago

    You're correct that nesting namespaces is unlikely to introduce measurable performance degradation. For performance, I was thinking mostly in the nested virtual network stack adding latency. Both docker and lxc run their own virtual interfaces.

    There's also the issue of running nested apparmor, selinux, and/or seccomp checks on processes in the child containers. I know that single instances of those are often enough to kill performance on highly latency sensitive applications (SAP netweaver is the example that comes to mind) so I would imagine two instances of those checks would exacerbate those concerns.

    [–] targetx@programming.dev 2 points 1 month ago

    Thanks for the tip, for some reason I assumed I couldn't run docker in LXC but never actually tried... I prefer to avoid the overhead of a full VM and I find LXCs way easier to manage from the host system. Guess I'll have something to test this weekend. Cheers!