diff options
author | Lars Wirzenius <liw@liw.fi> | 2024-04-22 17:07:40 +0300 |
---|---|---|
committer | Lars Wirzenius <liw@liw.fi> | 2024-04-22 17:07:40 +0300 |
commit | 08ab7750e7868c529c9d732e8c5d1f55cc413b7e (patch) | |
tree | 8b915509f51d2f38bb97ad3a045855fecbfbb199 | |
parent | 51034209deb8fe3b96e9efdefc9c03b9ffafddfb (diff) | |
download | vmdb2-08ab7750e7868c529c9d732e8c5d1f55cc413b7e.tar.gz |
docs: clarify that vmdb2 does not support containers
Signed-off-by: Lars Wirzenius <liw@liw.fi>
Sponsored-by: author
-rw-r--r-- | vmdb2.md | 7 |
1 files changed, 7 insertions, 0 deletions
@@ -140,6 +140,13 @@ Due to the kinds of things vmdb2 does (such as mounting, creating device nodes, etc), it needs to be run using root privileges. For the same reason, it probably can't be run in an unprivileged container. +Running vmdb2 in a container, privileged or not, is not supported. If +it works, that is a happy accident. There are no tests to make sure +that works, however, and no patches to make vmdb2 work in a container +will be considered for merging. This is because vmdb2 is maintained by +Lars, who has no use for containers, and does not want the maintenance +burden of having code that supports that. + ## Setting the hostname |