Docker Swarm VS LXC

Docker Documentation

When I sought help, a senior engineer simply asked, “Did you deploy it using Docker?” That’s when it hit me: I had missed a critical step. Determined to fix my mistake, I cleaned up the server, removed all dependencies and tools installed initially, and started fresh. This time, I focused on learning Docker.

The official Docker documentation is your comprehensive guide to all things Docker. While it might seem obvious, it's worth highlighting that this is one of the best-maintained technical documentations out there.

Docker Docs

Docker Docs: https://docs.docker.com/

Docker installed on your machine (Install Docker).

We will talk about downloading and getting to run Docker in our next session, but for now feel free to explore their resources on their website!🥰

Docker Documentation

I don't recommend using docker.io today as it will install an older version (at the time of writing this post, it is 24.0.7 on Ubuntu 22.04) and most of the tutorials will show you features based the official version and the official documentation.

I hope this doesn't affect LXC negatively.

LXC and LXD share plenty of contributors.

https://github.com/lxc/lxc/graphs/contributors

https://github.com/canonical/lxd/graphs/contributors

I use an "unprivileged LXC container" setup on several Debian bullseye hosts. It works fantastic, and each LXC container feels like a real server.

Compare that to Docker's "one-container-one-process" philosophy, reinventing the wheel by awkwardly composing multiple containers.

There is an issue with lxc as stated here: https://github.com/lxc/lxc/issues/4283 and https://github.com/Vanilla-OS/apx/issues/118

I'm currently attempting to enroll my Ubuntu (20.04) (Unprivileged) LXC hosts to my windows AD server but am having difficulty. I'm using SSSD and KRB5 to manage the user directory and authentication. Once joining the domain with realmd, all seems ok, I can use the id command, etc to lookup users and groups and the host appears in Windows Users and Computers. The issue I'm having is with authentication, I believe it to be related to this issue however I don't entirely understand the solution and can't seem to find much else on the matter (Note the method I'm using works fine on full VMs). Would anybody please be able to provide more clarity in layman's terms?

I don't recall having to do any uid/gid fixup last time I made an unprivileged container. I did have to prepare the unprivileged host user, of course, by reserving a range of subordinate uids/gids (/etc/sub?id) and configuring a virtual network interface limit (/etc/lxc/lxc-usernet).

To create the container, I did this:

lxc-create -t download -n -- -d debian -r bullseye -a amd64

Note that this runs the 'download' template, which (IIRC) is better suited to unprivileged containers than the 'debian' template is. The 'download' template will list its available distros if you do this:

lxc-create -t download -n -- --list

Note that some versions of lxc-create may fail with a keyserver error because sks-keyservers.net died somewhat recently. Workaround: DOWNLOAD_KEYSERVER=hkp://keyserver.ubuntu.com lxc-create

https://github.com/lxc/lxc/issues/3894

Found this issue and edited the config file of the lxc container:

and on this thread... an different approach is described

https://github.com/lxc/lxc/issues/1629#issuecomment-311379508