How can I solve the "load config failed, config.toml not found" error?

---

Error message

When deploying CubeBackup using Docker, you may encounter an error where the container fails to start and logs:

load configure failed:open /opt/cubebackup/etc/config.toml: no such file or directory

This typically indicates that the required configuration file is missing due to improper bind mounts in your CubeBackup container.

By default, CubeBackup automatically generates this config.toml file when the container is first started. However, if the bind mounts for /opt/cubebackup/etc is mapped to an empty directory on the host, it will overwrite the original configuration directory inside the container, resulting in this error.

How to resolve the issue

You can resolve this issue using either of the following methods:

• Start a new container with named volumes: You can deploy a new CubeBackup container, using named volumes instead of bind mounts for the /opt/cubebackup/etc directory. This ensures that the configuration file is preserved correctly. Please refer to the deployment example of CubeBackup in our documentation: Installation Guide for Docker users.

• Manually upload a config.toml file: Alternatively, you can download the default config.toml here and move it to the mounted directory on your host machine corresponds to /opt/cubebackup/etc/config.toml, and modify the permission if necessary.

  After uploading, please restart the CubeBackup container and verify that it starts correctly.

We are here to help

If the issue persists, please feel free to contact our support team at [email protected].