commit b54175d5acdf9bc1f52694e57908eaa35d5ccc56
parent 5556c4b3d8c8c3c60cb70131d9dc6645cd8c891c
Author: pyratebeard <root@pyratebeard.net>
Date: Wed, 26 Jan 2022 23:38:23 +0000
multi_lxc_with_haproxy
Diffstat:
1 file changed, 8 insertions(+), 0 deletions(-)
diff --git a/entry/multi_lxc_with_haproxy.md b/entry/multi_lxc_with_haproxy.md
@@ -0,0 +1,8 @@
+Near the beginning of last year I hit a few issues with some of my docker containers and part of my CI/CD pipeline. Around the same time I seemed to be reading more about LXC, and a few people on IRC mentioned it. I decided to take a step back from Docker and give LXC a go.
+
+## what the chroot
+LXC or Linux Containers, is a virtualisation method allowing the kernel to be used between multiple environments or containers. While traditionally with Docker you would run applications inside a container then network them together (web server, database, etc.) LXC gives you a "full" Linux system but unlike a virtual machine it shares the same kernel as the host.
+
+There are pros and cons to LXC but I don't want to get into that in this post. If you would like to know more about LXC check out the [official website](https://linuxcontainers.org). I should also point out that I have stuck with LXC and not LXD, which is a next generation container manager.
+
+## virtualise all the things
