Comment

Comment on Linux Containers Forks LXD Project As "Incus"

9488fcea02a9@sh.itjust.works ⁨1⁩ ⁨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

source

Sort:hotnew top

InvertedParallax@lemm.ee ⁨1⁩ ⁨year⁩ ago
Docker is spaghetti-ware, they try to control everything, which ironically makes me Isolate my dockers in a vm.

source
- 9488fcea02a9@sh.itjust.works ⁨1⁩ ⁨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
  
  source
  - InvertedParallax@lemm.ee ⁨1⁩ ⁨year⁩ ago
    Haven’t done that, but honestly I’m thinking that’s my next workflow.
    
    source
- jecxjo@midwest.social ⁨1⁩ ⁨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.
  
  source
phx@lemmy.ca ⁨1⁩ ⁨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

source