In an EGroupware standard installation, MariaDB is installed, configured and operated as a Docker container.
This presentation provides information about the reasons and advantages:
(lecture in German, slides in English)
The database container runs in the Docker network and is not directly accessible from the host or external network. This is also a security feature.
As a rule, it is not necessary to make changes to the database. However, there are sometimes situations that require this…
Always make a data backup before working on the database:
Backup of EGroupware
There are several ways to administer the database:
Database in the host network
To access or contact the database, the database must be made accessible outside the Docker network.
To do this, the following must be added to the
/etc/egroupware-docker/docker-compose.override.yml
the entry under service:
db:
ports:
- "127.0.0.1:3306:3306"
must be added.
Afterwards, the container must be restarted:
cd /etc/egroupware-docker
docker-compose restart
The database is now accessible on the host system under port 3306.
Working in the database container.
Another possibility is to enter the database container. To facilitate this, a script is available under:
/etc/egroupware-docker/mysql.sh.
Use phpMyAdmin
For graphical administration of the database, phpMyAdmin can also be used.
The installation/configuration of phpMyAdmin is prepared and can be installed as a Docker container.
The instructions can be found on the installed system or on GitHub:
Care should be taken to stop phpMyAdmin after use (as described in phpmyadmin.yml). Otherwise you open up a potential attack surface on the database.
A cron job that stops the container at a certain time (after work, in the evening, …) provides additional security (in case you forget).
For questions, suggestions etc. please create a separate topic in the forum and refer to this article.
