Backup and Restore Errors
This guide helps you address common errors encountered while using
appsmithctl, a command-line utility for backup and restore operations.
Service 'appsmith' is not running container
When attempting to execute
appsmithctl commands, you may face this error even if the appsmith service is up and running.
This error may occur even if the Appsmith service is up and running because the
docker-compose command was not used to start the Appsmith container. Hence, Appsmith is not registered with Docker Compose, making it inaccessible while running the
To resolve this issue, follow these steps:
- Stop the current Appsmith container with:
docker stop appsmith
Wait for the container to stop before proceeding.
- Go to the directory containing the
docker-compose.ymlfile using the
/path/to/docker-compose/directory with the actual path to the file.
- Start Appsmith with Docker-Compose using the
docker-compose.ymlfile in the current directory. Run the below command to start the Appsmith container:
docker-compose up -d
-d flag runs the containers in detached mode, allowing them to run in the background.
After completing these steps, Docker Compose will register the Appsmith container, resolving the error. The
appsmithctl commands should now work as expected.
If you are unable to resolve your error, please reach out to support via the chat widget on the page.