• @[email protected]
    link
    fedilink
    English
    71 year ago

    I used to use LXC maybe 5 years ago but I’ve since replaced everything with docker/compose. The main difference between LXC and Docker is that LXC is meant to be more like a Virtual Machine than a container. LXC containers run their own instance of systemd and can run multiple processes easily. Docker is meant to run a single process although people sometimes do hacks with supervisord or s6 overlay to run multiple processes.

    At the time LXC didn’t really have a concept of images like Docker, it was just base images like Ubuntu 18.04 or Debian 9 and you’d shell in the container and install your stuff.

    LXD is a tool built on top of LXC, confusingly enough the LXD client is called lxc… It’s higher level and might have the ability to use images, not sure, I never felt the need to learn it.

    • @[email protected]
      link
      fedilink
      English
      61 year ago

      I’ve always used lxc and only recently tried docker.

      I really cant wrap my head around all the crazy shit docker alters on your network settings like rewriting a bunch of firewall rules without telling you

      Not sure if i was doing something wrong but that was my experience with docker

      • @[email protected]
        link
        fedilink
        English
        61 year ago

        Docker is spaghetti-ware, they try to control everything, which ironically makes me Isolate my dockers in a vm.

        • @[email protected]
          link
          fedilink
          English
          41 year ago

          Ok, i’m glad my solution to the problem (run docker in an lxc container) isn’t as harebrained as i thought

          Other people are doing the same

        • jecxjo
          link
          fedilink
          English
          21 year ago

          That is kind of the expected setup. Either a vm or a dedicated system. You let docker do its thing and it should work.

          I run lxc because i want contained systems I control. That just means I have to do the work too.

          • @[email protected]
            link
            fedilink
            English
            21 year ago

            Same, I love lxc like I love jails, you craft beautiful systems that are isolated and clean.

            I wouldn’t make a disposable jail, but I make disposable lxcs, lxcs are like temporary distros for me.

            • jecxjo
              link
              fedilink
              English
              21 year ago

              There are scripts for making a jail around single apps but yeah I typically don’t use them that way. Lxc I very often install an app I want to test out and toss once I want to dedicate compile time to it.

              • @[email protected]
                link
                fedilink
                English
                11 year ago

                Yeah, I’d want a jail dockerfile system too, I just usually do them manually. Still, a way to run dockerfiles to build jails would be epic if you could make it work.

                I used gentoo for a decade, I just can’t afford the downtime if my workstation goes down, so it’s debian with lxc workspaces for a while, but gentoo actually runs well under lxc.

                Mostly every app expects its own distro, either debian or centos, few actually are agnostic, so getting them to run on gentoo was always more of a challenge than on raw debian/Ubuntu.

                • jecxjo
                  link
                  fedilink
                  English
                  31 year ago

                  I’m actually the opposite. Run gentoo as my host and toss up a debian lxc if needed. Worst case scenario im running just the kernel and everything else from a container (actually how i typically run when rebuilding a system from start).

                  I’ve never run into a situation where an app “couldn’t” run in Gentoo. It’s just that I’ve had cases where an app is build for a 8 year old LTS of debian with such old dependencies it wouldn’t be worth my time building them all when i can just pull up a container with that super old build. The nice thing is that all the vulnerabilities that old Debian had is now in a container and less of a target.

                  I swear i must be lucky cuz i do often hear of gentpo fatigue but I’ve been running it since the project started and never had issues outside the things they legitimately broke.

                  • @[email protected]
                    link
                    fedilink
                    English
                    11 year ago

                    Back around, I want to say more than a decade ago, they changed some stuff in the portage tree and everything broke hard for me. Then I rebuilt and a few weeks later it broke again. This was when maintainers changed and they were pretty angry for some reason.

                    I bailed because I couldn’t build, I don’t remember all the details, it just seemed like they didn’t care, and I suddenly got really busy.

                    I’d like to go back, but debian with lxc children has been so good to me, by now there’s nothing else to really learn (though of course I hate systemd), I’m using the same system as on half my servers, then freebsd for the others.

                    I’ve been using gentoo lxc to put my toes back in the water, just upgraded my workstation to a monster, might switch back, I suppose the main thing stopping me is how well debian has treated me for the last while, even most ubuntu targeted software runs out of the box.

                    Also, I’m really terrified of changes that lead to build breaks, any time I have to rebuild is a problem, I need my main workstation to control everything, so it’s a place I’m willing to lose some customization for more stability nowadays.

                    Ironically my only major applications are basically konsole, Firefox, dolphin and python for the pyqt5 gui apps i wrote like a video player and some other stuff, though getting back into lutris would be nice too.

      • @[email protected]
        link
        fedilink
        English
        41 year ago

        This is the same issue I have. I much prefer to manage my own firewall policies and having to make those play nicely with Docker was a huge pain in the ass in most cases. I’d rather use snaps than Docker for stuff that requires a daemon and regular updates, and Snaps have plenty of issues as well