This is a Docker image for Roundcube WebUI. The project is part of the docker-mailserver project but can run separately without the other components. However, a database server is always required to store data.
Related images:
- docker-mailserver - The main project, containing composition instructions
- docker-mailserver-postfix - Postfix/Dovecot image (mailserver component)
- docker-mailserver-opendkim - OpenDKIM image (DKIM signing milter component)
- docker-mailserver-postfixadmin - Image for PostfixAdmin (Web UI to manage mailboxes and domain in Postfix)
- docker-mailserver-amavis - Amavis, ClamAV and SpamAssassin (provides spam and virus detection)
The following versions are available from DockerHub. The image tag matches the Roundcube version.
- 1.6.6.0, 1.6.6, 1.6, 1, latest - Dockerfile
- 1.5.2.0, 1.5.2, 1.5 - Dockerfile
- 1.4.11.0, 1.4.11, 1.4 - Dockerfile
- Database and Roundcube setup from environment variables
docker-mailserver-roundcube is licensed under GNU LGPL 3.0. As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).
As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.
The following components must be available at runtime:
- MySQL >8.0 or MariaDB >10.4 - used as database backend for domains and mailboxes.
docker-mailserver-roundcube requires various environment variables to be set. The container startup will fail when the setup is incomplete.
| Variable | Description | Default Value |
|---|---|---|
RC_DB_HOST |
The hostname or IP address of the database server | |
RC_DB_USER |
The name of the database user. Attention! You shall not use an administrator account. | |
RC_DB_PASS |
The password of the database user | |
RC_DB_NAME |
The name of the database | |
RC_DES_KEY |
This key is used to encrypt the users IMAP password which is stored in the session record (and the client cookie if remember password is enabled). Please, provide a string of exactly 24 chars. | |
RC_IMAP_SERVER_NAME |
The hostname of the IMAP server for picking up e-mails. | |
RC_SMTP_SERVER_NAME |
The hostname of the SMTP server fpr sending e-mails. | |
RC_DEFAULT_DOMAIN |
The default mail domain to be used. This saves typing effort when logging in for this domain as you only need to input the mailbox name. |
docker-mailserver-roundcube exposes port 80 (the WebUI). No TLS support is built in. So you shall put your container behind an Ingress or Reverse Proxy that enforces HTTPS.
The main mailserver project has examples of container configurations:
Once you have started your Roundcube container successfully, follow these instruction to setup your instance:
- Login to your database and create the Roundcube user with password and the appropriate database (values from your enviroment variables).
- Log into the container and edit file
/var/www/html/config/config.inc.php. Enable the installer by setting$config['enable_installer'] = true;(line 113). - Navigate in your browser to
/installer/. - Check the setup and click Next.
- Check that the database config is OK at "DSN".
- Click the "Initialize database" button to create the DB schema.
- Test the SMTP and IMAP configs and make adjustments if required
- Log into the container and edit file
/var/www/html/config/config.inc.phpagain. Disable the installer by setting$config['enable_installer'] = false;(line 113).
Now you can navigate to / in your browser and login with your mail account credentials.
You can further customize config.inc.php. Please follow these instructions:
- Get a copy of the file from the
/var/www/htmlfolder. - Customize your configuration file.
- Provide your customized file back into the
/var/www/htmlby using a volume mapping.
This Docker image is mature and supports my own mailserver in production. There are no known issues at the moment.
Report a bug, request an enhancement or pull request at the GitHub Issue Tracker. Make sure you have checked out the Contribution Guideline