Doesn't start on WSL2
Closed this issue · 0 comments
m-mohr commented
Problem description
I'm trying to run this on Ubuntu through WSL2 (Windows Subsystem for Linux, v2):
mm@Matthias-Workstation:/mnt/c/Dev/eoAPI$ docker compose up
WARN[0000] The "AWS_ACCESS_KEY_ID" variable is not set. Defaulting to a blank string.
WARN[0000] The "AWS_SECRET_ACCESS_KEY" variable is not set. Defaulting to a blank string.
[+] Running 5/5
✔ Network eoapi-network Created 0.0s
✔ Container eoapi.db Created 0.0s
✔ Container eoapi.raster Created 0.6s
✔ Container eoapi.vector Created 0.6s
✔ Container eoapi.stac Created 0.0s
Attaching to eoapi.db, eoapi.raster, eoapi.stac, eoapi.vector
eoapi.db | chmod: changing permissions of '/var/lib/postgresql/data': Operation not permitted
eoapi.db | The files belonging to this database system will be owned by user "postgres".
eoapi.db | This user must also own the server process.
eoapi.db |
eoapi.db | The database cluster will be initialized with locale "en_US.utf8".
eoapi.db | The default database encoding has accordingly been set to "UTF8".
eoapi.db | The default text search configuration will be set to "english".
eoapi.db |
eoapi.db | Data page checksums are disabled.
eoapi.db |
eoapi.db | initdb: error: could not change permissions of directory "/var/lib/postgresql/data": Operation not permitted
eoapi.db | fixing permissions on existing directory /var/lib/postgresql/data ...
eoapi.db exited with code 1
eoapi.vector | wait-for-it.sh: waiting 120 seconds for database:5432
eoapi.raster | wait-for-it.sh: waiting 120 seconds for database:5432
eoapi.stac | wait-for-it.sh: waiting 120 seconds for database:5432
eoapi.vector | wait-for-it.sh: timeout occurred after waiting 120 seconds for database:5432
eoapi.raster | wait-for-it.sh: timeout occurred after waiting 120 seconds for database:5432
eoapi.stac | wait-for-it.sh: timeout occurred after waiting 120 seconds for database:5432
eoapi.vector exited with code 124
eoapi.raster exited with code 124
eoapi.stac exited with code 124
Expected Output
eoAPI starts. I assume this might be related to https://stackoverflow.com/questions/44878062/initdb-could-not-change-permissions-of-directory-on-postgresql-container
Environment Information
OS: Windows 10 -> WSL2 -> Ubunto 22.04.2
It starts without issues on Windows itself.