LXC/LXD support instead of Docker
Feature Request
Feature Information:
I hereby request support for LXC/LXD Containers (https://linuxcontainers.org/lxd) in addition to Docker Containers, since it is much more versatile than docker and comes with far less issues and incompatibilities. Some features I require over Docker, that make LXC/LXD superior (in my eyes):
- doesn't reset iptables on restart
- can do backups and snapshots using btrfs (and several more)
- much improved networking utils.
- Allows easy using of specific host interfaces
- Allows 'chaining' containers interfaces. (e.g. for recursive-vpns)
- networking better manageable while container is running
- better containerization compared to docker
- specifically does not have issues using systemd inside the container
- allows for actual virtualization (aka a VM) instead of plain containerization (if so desired and interchangeable)
I confirm:
- [x] that I have searched for an existing feature request matching the description.
- [x] that my checkboxes above look like the one on the left (remove this line when done)
AMP can already run fine in LXC/LXD containers. That’s how I deploy AMP. So I’m not sure what you are asking for? If you are looking for AMP itself to install and configure LXC/LXD, create a container, and then install itself in the container, I don’t think that is really feasible.
@Greelan I think he want lxc Support beside Dockersupport
@gOOvER yeah, I did get that from the title lol. But that still doesn't answer what "support" means. It's like asking for AMP to support VMs. Does the OP want AMP to turn into something like Proxmox? I just don't see it happening
I mean to support LXC Containers in the same way as Docker Containers for Game Instances.
It can't work in the same way. LXD/LXC containers are system containers, not application containers like Docker. So for it to work with AMP, you would effectively be creating separate target installations of AMP for each game server, and then managing them by a controller AMP installation on the LXD/LXC host or somewhere else. It's a bit like having a separate host for each game server
It can't work in the same way. LXD/LXC containers are system containers, not application containers like Docker. So for it to work with AMP, you would effectively be creating separate target installations of AMP for each game server, and then managing them by a controller AMP installation on the LXD/LXC host or somewhere else. It's a bit like having a separate host for each game server
which is as it should be. If you don't do the same with the docker application containers, you are actually using them wrong and discarding the isolation they provide entirely. (regarding running an additional AMP/ADS inside the container and only communicating using sockets)
I'm going to drop this due to a lack of interest relative to the amount of work required. If demand for this picks up I may revisit it, but other users have been running the whole of AMP happily in LXC containers so I don't see the need to increase the support footprint.