Notices tagged with lxc
-
@mangeurdenuage I don't know how they ( #Docker, #LXC, #Virtuozzo / #OpenVZ ) would deal with that, since (as #BSD fans are quick to point out) containers in Linux lack appropriate security controls.
-
No energy for the system setup today, but I do eventually intend to run #Proxmox, #LXD, and #Flynn on the server rack to my left.
Proxmox: https://pve.proxmox.com/wiki/Main_Page
LXD and #LXC: https://linuxcontainers.org/lxd/ and https://linuxcontainers.org/lxc/
Flynn: https://flynn.io/
-
@clacke@libranet.de@libranet.de @musicman I don't see many spittle-spraying Docker enthusiasts anymore. Nowadays, it is more of "why aren't you using Docker? That's the way to go". Personally, I'm hoping to explore #LXC (partly through #LXD), #Proxmox, #KVM, #Xen soon.
-
yoink! Another service moved to #lxc. This time, #nextcloud.
-
Converted the blog from #Jekyll to #Hugo, moved it to #LXC container, hooked-up #DroneCI to auto-deploy when pushing changes to #Gitea. Next up is to test the #micropub workflow, but for now I'm going to bed :)
-
Well, I guess #ansible doesn't work in a #lxc container: "ERROR! Unable to use multiprocessing, this is normally caused by lack of access to /dev/shm: [Errno 2] No such file or directory"
-
Moved #unifi controller in #lxc container
-
neat. Setup a #pihole #lxc container on the desktop while I take my #raspi offline for some shenanigans.
-
Status: Playing with #lxc / #lxd
-
@moonman @drymer Oh but the 3 EUR one probably has pretty severe limitations that make it not worthwhile. I'd guess a very strict CPU and memory throttling policy, slow I/O, bandwidth limitations etc... Might as well go for a 10EUR one where you can run your own set of #lxc virtual servers etc. etc. and decide the restrictions yourself - you can probably run more stuff…
LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864}
Chimo
MMN-o ✅⃠
All Hacker Poesy content and data are available under the