Skip to content

Latest commit

 

History

History
54 lines (36 loc) · 2.49 KB

UPDATING_SERVICES.md

File metadata and controls

54 lines (36 loc) · 2.49 KB

Updating services

The process is relatively simple. As soon as a new version of any of the services is released, it's enough to edit your .env file pointing to the new version and redeploy the service.

In a recurrent way we update the versions in the repository, so that we also run the automatic builds and we make sure that the deployment process with docker continues working. If at some point there is a new version and the repository has not been updated, you can try to do it on your local and feel free to contribute by opening a merge request with your changes.

How to update a service

Our suggestion is to do it one at a time, verifying by yourself the corresponding Dockerfile and making sure that the service is updated correctly.

The steps are exactly the same for all of the services. So you can follow the steps below just replacing the service name. For this example, the service is tor and it will be updated from version 12.0.3 to version 12.0.4.

Go to your .env file and edit the version parameter:

# TOR_VERSION=12.0.3 -- before
TOR_VERSION=12.0.4

Next, stop the service and re-run it.

$ docker-compose stop tor
$ docker-compose up -d tor

Check the logs o be sure that the service starts correctly.

$ docker ps | grep tor
# 06a96296854a   tor:12.0.4
$ docker logs 06a96296854a -f

If after a while you see that the service is working properly, you can delete the old image.

$ docker images | grep tor
# REPOSITORY         TAG           IMAGE ID       CREATED         SIZE
# tor                12.0.4        236c6c6b89da   7 minutes ago   90.2MB
# tor                12.0.3        7ad38075c199   4 weeks ago     90.2MB
$ docker rmi 7ad38075c199

Troubleshooting

In case that something goes wrong during this process, it can be for two reasons:

  • Either something has changed in the service and the Dockerfile is not able to rebuild the image. In that case, we will have to review and update the build process in the project.
  • The build process is fine but there is a problem with the service or your configuration.

In both cases, you can go back to the previous version that was working before. So simply revert the steps: put the previous version back in the .env file and re-run the service. The container you had previously will be deployed and everything should work again.

In the meantime, you can open a thread in the Discussions section so we can help you.