v
Size: a a a
v
IS
People think of containers as if it was some magical black box where anything can happen. It's just a process running in bunch of namespaces for isolated processes, filesystem or network.
To add some perspective: if you run your DB server as systemd service, (with most major distributions this is the case) you are already running the DB in a container. Arguably much less restrictive one, but still technically a container, if you try to limit the service to bare minimum, you would end up with something almost on par with docker. (from DB's point of view)
Obviously I'm oversimplifying a bit, but the real questions should be whether specific process/network/filesystem namespace will have any impact, which is more specific question that might have some useful answer compared to just looking at docker with black box mindset.
But yeah, generally speaking most of your worries should be the same as you would have with regular system service.
v
v
v
YC
v
v
yg
yg
NN
YC
E
p
p
p
p
p
E
p