FAQ¶
List of frequently asked questions. If your question is not listed or the instructions are unclear / do not solve your problem, please feel free to contact us.
How to get started¶
The best starting point to get to know the microservices is the tutorial deployment repository. Instructions on how to use it can be found here.
How to contact the developers¶
The best way to contact the developers is via mattermost. There are dedicated channels for some of the microservices in the itksw group. There are also more general user and developer channels for topics not covered by the above mentioned channels in the ITkPixel group.
Direct links to the mattermost channels:
In addition to these channels there is the atlas-itk-demo-sw-devel e-group. The e-group is used to annouce our weekly meetings (currently wednesday at 17:00). These meetings are focussed on development but user feedback is always welcome.
Microservices are not showing up in dashboard¶
To have the microservices listed in the dashboard the itk-demo-registry microservice needs to be running. Please ensure that the respective container is started. To register microservices container the service-registry needs certain labels to bet set in each docker compose file. A list of these can be found here under the bullet point registrator.
Link to microservice in dashboard is not working/showing up¶
Broken or none-existent links in the dashboard are most commenly caused by a wrongly configured ${HOST} variable. Most compose files use the HOST env var as the hostname by default. Please make sure that this variable is correctly set in the env vars, the .env file or directly in the docker compose file.
The host variable should always point to the fully qualified domain name (e.g. wupp-charon.cern.ch)
Microservices that are not running are showing up in the dashboard¶
In older version of the itk-demo-registry some labels might not be correctly removed when stoping a container. This causes services to show up in the dashboard even after their container was stoped. To avoid this please update to the newest version of the itk-demo-registry and to remove old leftover labels, restart the etcd container.
ERROR: 401 Authorization Required when pulling from CERN registry¶
Authentication is now required when pulling images from the CERN gitlab registry or harbor cache. Follow this guide for instructions. NOTE: use your CERN username, but CLI secret as password (as described in guide).
ERROR: Network deminet declared as external, but could not be found.¶
The deminet docker network is the network the microservices use to communicate with each other. It has to be created once on every host running docker containers. You can do so with:
ERROR: while creating mount source path ... permission denied.¶
When trying to access a bind-mount on some drives the following error might occur during the execution of the config script:
docker: Error response from daemon: error while creating mount source path ... permission denied.
This is issue is caused when the docker user has no rights on the mounted drive.
Some containers like mariadb for the configdb or portainer need a bind-mount to persistently save their data. To fix this issue for these containers please make sure to use a directory where the root user has access. By default most compose files use the directory of the microservice/deployment stack is used. You can change the mount location directly in the compose file under volumes.