@@ -18,6 +18,7 @@ After signing in you should run 'Re-check and refresh configuration' (should be
## Known Bugs
- Virtualmin does not work with S6 init, need to switch init systems.
- This image (particularly the initialisation script) is not well tested on existing data/config. If you do try to import something, make sure you have a backup of it first.
- This also applies to updating to newer versions of this image. **Assume everything is un-tested and un-supported. Back up everything.**
- ClamAV-Freshclam runs on a cron job defined in the image, this means *every* instance of this image will try to update Clam at the same time unless you change the defaults.
...
...
@@ -25,7 +26,7 @@ After signing in you should run 'Re-check and refresh configuration' (should be
- The build process should not be sending the entire directory as context, just root would do.
- The initialisation script will set all notification e-mail addresses to admin@container-domain, this may not be what you want. Refer to root/etc/cont-init.d/50-virtualmin-config for a list of the files where this is set.
- The initialisation script will also change ownership of a bunch of files and directories in /config to root:root, this might make a mess of existing data and I'm not really sure this is valid any more (feels like an old hack for permissions issues that may or may not still exist or could be handled better).
- Something (I suspect docker) messes with the permissions in /etc, and that upsets quite a few things. DKIM refuses to work.
- Something (I suspect docker) messes with the permissions in /etc, and that upsets quite a few things. DKIM refuses to work, because Virtualmin assumes the config lives in the default location and cannot be overridden.
- Running 'passwd' in the container will fail because /etc/shadow is actually a symlink, Webmin can manipulate the file just fine (I'm probably breaking some fundamental *nix concept here).
- A number of features are installed directly in the container when really they should be separate containers that Virtualmin can link to (e.g. MySQL, ClamAV, SpamAssassin, and so on), and which probably have perfectly good images I could direct you to.
- The Webmin certificate is generated during image build, this means all containers share the same default certificate which is bad for security.
