You are here

Checking system start up

Use this information to verify that the system started correctly, and to clean up the deployment.

Before continuing, make sure that you've completed the steps in Deploying using Docker Compose.

  1. Open a new terminal window.
  2. Change directory to the docker-compose folder that you created in the deployment steps.
  3. Verify that all the services started correctly.
    1. List the images and additional details:

      docker-compose images

      You should see a list of the services defined in your docker-compose.yaml file:

              Container                           Repository                           ...     Size 
      --------------------------------------------------------------------------------------------------
      acs-trial_activemq_1                alfresco/alfresco-activemq                   ...   447 MB 
      acs-trial_alfresco-pdf-renderer_1   quay.io/alfresco/alfresco-pdf-renderer       ...   625 MB 
      acs-trial_alfresco_1                alfresco/alfresco-content-repository         ...   1.02 GB
      acs-trial_digital-workspace_1       quay.io/alfresco/alfresco-digital-workspace  ...   27.1 MB 
      acs-trial_imagemagick_1             quay.io/alfresco/alfresco-imagemagick        ...   698 MB 
      acs-trial_libreoffice_1             quay.io/alfresco/alfresco-libreoffice        ...   1.46 GB
      acs-trial_postgres_1                postgres                                     ...   274 MB 
      acs-trial_proxy_1                   quay.io/alfresco/alfresco-acs-nginx          ...   16.9 MB
      acs-trial_share_1                   alfresco/alfresco-share                      ...   681 MB 
      acs-trial_shared-file-store_1       alfresco/alfresco-shared-file-store          ...   435 MB 
      acs-trial_solr6_1                   alfresco/alfresco-search-services            ...   900 MB 
      acs-trial_tika_1                    quay.io/alfresco/alfresco-tika               ...   743 MB 
      acs-trial_transform-router_1        quay.io/alfresco/alfresco-transform-router   ...   574 MB
    2. List the running containers:

      docker-compose ps

      You should see a list of the services defined in the docker-compose.yaml file.

    3. View the log files for each service <service-name>, or container <container-name>:

      docker-compose logs <service-name>
      docker container logs <container-name>

      For example, to check the logs for Share, run any of the following commands:

      docker-compose logs share
      docker container logs acs-trial_share_1

      You can add an optional parameter --tail=25 before <container-name> to display the last 25 lines of the logs for the selected container.

      docker-compose logs --tail=25 share
      docker container logs --tail=25 acs-trial_share_1

      Check for a success message:

      Successfully retrieved license information from Alfresco.

    Once you've tested the services, you can clean up the deployment by stopping the running services.

  4. Stop the session by using CONTROL+C in the same window as the running services:

    ^CGracefully stopping... (press Ctrl+C again to force)
    Stopping acs-trial_transform-router_1      ... done
    Stopping acs-trial_proxy_1                 ... done
    Stopping acs-trial_alfresco-pdf-renderer_1 ... done
    Stopping acs-trial_activemq_1              ... done
    Stopping acs-trial_share_1                 ... done
    Stopping acs-trial_shared-file-store_1     ... done
    Stopping acs-trial_digital-workspace_1     ... done
    Stopping acs-trial_libreoffice_1           ... done
    Stopping acs-trial_solr6_1                 ... done
    Stopping acs-trial_imagemagick_1           ... done
    Stopping acs-trial_tika_1                  ... done
    Stopping acs-trial_postgres_1              ... done
    Stopping acs-trial_alfresco_1              ... done
  5. Alternatively, you can open a new terminal window, change directory to the docker-compose folder, and run:

    docker-compose down

    This stops the running services, as shown in the previous example, and removes them from memory:

    Stopping acs-trial_transform-router_1      ... done
    Stopping acs-trial_proxy_1                 ... done
    ... 
    Removing acs-trial_transform-router_1      ... done
    Removing acs-trial_proxy_1                 ... done
    Removing acs-trial_alfresco-pdf-renderer_1 ... done
    Removing acs-trial_share_1                 ... done
    Removing acs-trial_activemq_1              ... done
    Removing acs-trial_shared-file-store_1     ... done
    Removing acs-trial_postgres_1              ... done
    Removing acs-trial_solr6_1                 ... done
    Removing acs-trial_imagemagick_1           ... done
    Removing acs-trial_libreoffice_1           ... done
    Removing acs-trial_alfresco_1              ... done
    Removing acs-trial_digital-workspace_1     ... done
    Removing acs-trial_tika_1                  ... done
    Removing network acs-trial_default
  6. You can use a few more commands to explore the services when they're running. Change directory to docker-compose before running these:
    1. Stop all the running containers:

      docker-compose stop
    2. Restart the containers (after using the stop command):

      docker-compose restart
    3. Starts the containers that were started with docker-compose up:

      docker-compose start
    4. Stop all running containers, and remove them and the network:

      docker-compose down [--rmi all]

      The --rmi all option also removes the images created by docker-compose up, and the images used by any service. You can use this, for example, if any containers fail and you need to remove them:

      Stopping acs-trial_transform-router_1      ... done
      ... 
      Removing acs-trial_transform-router_1      ... done
      ... 
      Removing network acs-trial_default
      Removing image alfresco/alfresco-content-repository:6.1.0
      Removing image ...

See the Docker documentation for more on getting started with Docker and using Docker.

Sending feedback to the Alfresco documentation team

You don't appear to have JavaScript enabled in your browser. With JavaScript enabled, you can provide feedback to us using our simple form. Here are some instructions on how to enable JavaScript in your web browser.