4 ms·
I'm not convinced the memory usage would be very high.. but doing some measurements would be interesting. Avoiding network namespace and by using --net=host sh
by Daviey 10y ago
I'm not convinced the memory usage would be very high.. but doing some measurements would be interesting.
Avoiding network namespace and by using --net=host should allow dbus to run.
Allowing updatedb to look in /var/lib/docker/ (and any attached volumes) should mean that the host mlocate can see all the files within the container.
- oelmekki 10y agoAwesome, thanks Daviey. So it seems to me that, while there's indeed some heavy coding to do for things like keeping apps up to date, containerizing what haven't been yet and managing data containers / mounted volumes, there's nothing preventing such setup to be viable, with hard work. There probably should be some grouping done at some point I guess, to work around apps that expect to live in the same place to work together, but that's still doable. Do you see any big blocker?