Common problems & FAQ

Common problems

The container "cms" keeps restarting

This can have multiple reasons:

The database doesn't exist

Make sure that db/docker-entrypoint-initdb.d was correctly mounted to /docker-entrypoint-initdb.d inside the db container.

You can check this by executing docker-compose exec db sh and stat /docker-entrypoint-initdb.

If this folder is empty, Docker failed to create the mount for it. Make sure that Docker can access your hard drive. If you are in a Windows domain, make sure that the password of your windows user has not expired. You might have to re-enter it.

The database structure can't be created

If the database was deleted, make sure to delete all files in cms/dbfiles/, because the database import will fail when this folder is not empty.

The CMS can't be accessed in my browser

Sometimes, the Apache process fails to restart in the cms container. At the moment we do not know what causes this. It seems to be Docker bug.

Full hard disk

Containers fail to start when your hard disk is full.

Be sure that you have sufficient disk space.

The container "elastic" doesn't start

Be sure that you have enough memory (default setting is 2GB) available on your system. When using Virtualbox, it might be necessary to give the Virtual box container more memory.

FAQ

How do I reset the data?

• docker-compose down
• Delete all files in cms/dbfiles/
• Delete all files in db/data/