Make docker volume paths configurable.

[JonasGilg]

Description

It is now possible to specify the docker volume path via the .env file.

[annawendler]

You say it is possible to set the VOLUME_DIR in the .env file. This is not clear to me. Can you adapt the .env template?

[github-actions]

Test Results

39 tests  ±0   39 ✅ ±0   11s ⏱️ ±0s
17 suites ±0    0 💤 ±0 
 1 files   ±0    0 ❌ ±0 

Results for commit 6d38a12. ± Comparison against base commit d7dd9b8.

[JonasGilg]

You say it is possible to set the VOLUME_DIR in the .env file. This is not clear to me. Can you adapt the .env template?

Yes, I updated the .env templates. You can give a path, where docker should store all the data. It is required that the folder exists with the 3 subfolders mentioned in the comment in the .env template. It is not required anymore to create docker volumes with docker volume create!

[annawendler]

Thank you. I created a folder with the specified three subfolders and set the VOLUME_DIR in .env.docker and backend/.env. When running "USER_ID=$(id -u) GROUP_ID=$(id -g) docker-compose -f docker-compose.dev.yml up -d" I get "KeyError: 'ContainerConfig'". Do you have an idea where this is coming from?

[JonasGilg]

Thank you. I created a folder with the specified three subfolders and set the VOLUME_DIR in .env.docker and backend/.env. When running "USER_ID=$(id -u) GROUP_ID=$(id -g) docker-compose -f docker-compose.dev.yml up -d" I get "KeyError: 'ContainerConfig'". Do you have an idea where this is coming from?

I am not quite sure. If I remember correctly we had issues with the docker-compose files in the backend folder and just used the docker-compose file in the root folder. There you should also create an .env file with the same values.

Run this in the root folder: USER_ID=$(id -u) GROUP_ID=$(id -g) docker-compose -f docker-compose.yaml up -d

[annawendler]

I think the issue was some interference with the old volumes which I could solve. Now, when I want to run "USER_ID=$(id -u) GROUP_ID=$(id -g) docker-compose -f docker-compose.dev.yml run --rm backend python manage.py import_rki rki.zip" I get the error "django.db.utils.OperationalError: could not translate host name "db" to address: Name or service not known". I also noticed that I can't reach pgAdmin via the browser. Is there another path that needs to be adapted regarding the docker volumes? I couldn't solve this.