Skip to main content

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.

Error Message

Service 'appsmith' is not running container


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 theappsmithctl commands.


To resolve this issue, follow these steps:

  1. Stop the current Appsmith container with:
docker stop appsmith

Wait for the container to stop before proceeding.

  1. Go to the directory containing the docker-compose.yml file using the cd command :
cd /path/to/docker-compose/directory

Replace /path/to/docker-compose/directory with the actual path to the file.

  1. Start Appsmith with Docker-Compose using the docker-compose.yml file in the current directory. Run the below command to start the Appsmith container:
docker-compose up -d

The -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.

Getting help

If you are unable to resolve your error, please reach out to support via the chat widget on the page.