Sider Enterprise Release Note in November 2019
release-201911.5
From this release, you don't have to set up setaria component, which was used for performing analyses. Instead, Sider runs runners with Docker directly. Runners are just containers that perform analyses and they were executed by setaria component before. You should still take care of the Docker host performance issues, but direct usage by Sider reduces the maintenance of another component.
In addition, the way of downloading Docker images has changed. AWS credentials (AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY) are required when downloading images and the image names are also changed. See Get Docker Image for more details.
How to upgrade
If you set up Sider with docker-compose, removes setaria_web
and setaria_worker
services from the docker-compose.yml
. Also, you must allow sideci_worker
to call Docker API. If you want to sideci_worker
to access Docker via Unix socket, don't forget to attach Docker socket (e.g. /var/run/docker.sock:/var/run/docker.sock:ro
).
To upgrade to this release, the following environment variables are newly needed.
See each link for more details.
Generally, You can upgrade Sider following the steps:
- Download application images. See Get Docker Image
- Stop applications
- Update release tags on
docker-compose.yml
.- Replace older release tags with
release-201911.5
- Replace older release tags with
- Add the following instruction to the
sideci_worker
service
volumes:
- /var/run/docker.sock:/var/run/docker.sock:ro
- Remove
setaria_web
andsetaria_worker
services - Update the env file for
sideci_web
andsideci_worker
and includeRUNNERS_TRACES_S3_BUCKET_NAME
andDOCKER_RUNNERS_CONFIG
- Run migrations
- sideci for
docker-compose run sideci_web bundle exec rails db:migrate
- catpost for
docker-compose run catpost_web bundle exec rails db:migrate
- sideci for
- Start applications