Docker Compose deployment on mac #65

Open
opened 2025-06-30 12:19:53 +00:00 by RaoulKramer · 5 comments
RaoulKramer commented 2025-06-30 12:19:53 +00:00 (Migrated from gitlab.com)
No description provided.
RaoulKramer commented 2025-06-30 19:09:37 +00:00 (Migrated from gitlab.com)

The issue during installation on MacBook is:

  1. "The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested" for both polis-file-server, polis-math, and polis-server.

Just a minor adjustment in the docker compose file ("platform: linux/amd64" added under service: image).

  1. Error response from daemon: Mounts denied: The path /postgresql-data is not shared from the host and is not known to Docker.

Docker (on mac) doesnt substitute the ${ } vars in the dev.env file since it is not a shell environment

so I created (as a hack for now) "run-dev.sh":

#!/bin/sh
export ROOT_DIR=${PWD}
export DATA_DIR=${PWD}
export PARTICIAPI_DIR=${ROOT_DIR}/../particiapi
export PARTICIAPP_FRONTEND_DIR=${ROOT_DIR}/../particiapp-example-frontend
export POLIS_SERVER_NAME=polis.example.org
docker compose --env-file dev.env -f docker-compose.yaml -f docker-compose.dev.yaml up

chmod +x run-dev.sh

and then just ./run-dev.sh


After this, it was difficult to set Chrome with the parameters; easier to use Safari (and set it up with proxy)
I would suggest putting this section before starting the services

That way, when you start the service, you should see it in Safari immediately

The issue during installation on MacBook is: 1. _"The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested" for both polis-file-server, polis-math, and polis-server._ Just a minor adjustment in the docker compose file ("`platform: linux/amd64`" added under `service: image`). 2. _Error response from daemon: Mounts denied: The path /postgresql-data is not shared from the host and is not known to Docker._ Docker (on mac) doesnt substitute the ${ } vars in the dev.env file since it is not a shell environment so I created (as a hack for now) "`run-dev.sh`": ``` #!/bin/sh export ROOT_DIR=${PWD} export DATA_DIR=${PWD} export PARTICIAPI_DIR=${ROOT_DIR}/../particiapi export PARTICIAPP_FRONTEND_DIR=${ROOT_DIR}/../particiapp-example-frontend export POLIS_SERVER_NAME=polis.example.org docker compose --env-file dev.env -f docker-compose.yaml -f docker-compose.dev.yaml up chmod +x run-dev.sh ``` and then just `./run-dev.sh` ---- After this, it was difficult to set Chrome with the parameters; easier to use Safari (and set it up with proxy) I would suggest putting this section _before_ starting the services That way, when you start the service, you should see it in Safari immediately
RaoulKramer commented 2025-06-30 19:11:32 +00:00 (Migrated from gitlab.com)

assigned to @gberh

assigned to @gberh
gberh commented 2025-08-13 13:05:01 +00:00 (Migrated from gitlab.com)

This issue will soon become obsolete with the new version of the docker compose environment which uses git submodules rather than manual checkouts in a common base directory for which the $PWD was used.

This issue will soon become obsolete with the new version of the docker compose environment which uses git submodules rather than manual checkouts in a common base directory for which the `$PWD` was used.
RaoulKramer commented 2025-09-01 13:31:19 +00:00 (Migrated from gitlab.com)

signal-2025-08-28-215458_002

signal-2025-08-28-210649

@gberh this is feedback from @abihas (Michael) with Mac deployment.

@jgroenen do you had time to test?

![signal-2025-08-28-215458_002](/uploads/abed6373457668fef709f36f56336695/signal-2025-08-28-215458_002.png) ![signal-2025-08-28-210649](/uploads/895aa2e4ff245a7426414ef6737bb3bd/signal-2025-08-28-210649.png) @gberh this is feedback from @abihas (Michael) with Mac deployment. @jgroenen do you had time to test?
gberh commented 2025-09-03 06:16:26 +00:00 (Migrated from gitlab.com)

I am a bit at loss here, the project https://gitlab.com/particiapp/polis is public and the visibility settings for the Docker registry is set to "Everyone With Access". According to https://docs.gitlab.com/user/packages/container_registry/#container-registry-visibility-permissions anonymous access should be possible.
I just tried in a VM to run docker pull registry.gitlab.com/particiapp/polis/server:latest and that works without asking for credentials. Could you please try that as well?

I am a bit at loss here, the project https://gitlab.com/particiapp/polis is public and the visibility settings for the Docker registry is set to "Everyone With Access". According to https://docs.gitlab.com/user/packages/container_registry/#container-registry-visibility-permissions anonymous access should be possible. I just tried in a VM to run `docker pull registry.gitlab.com/particiapp/polis/server:latest` and that works without asking for credentials. Could you please try that as well?
RaoulKramer (Migrated from gitlab.com) closed this issue 2026-01-15 11:21:00 +00:00
RaoulKramer (Migrated from gitlab.com) reopened this issue 2026-02-20 16:40:07 +00:00
raoulkramer added this to the VoxitNL project 2026-06-10 12:25:58 +00:00
raoulkramer modified the project from VoxitNL to (deleted) 2026-06-10 12:56:10 +00:00
raoulkramer modified the project from (deleted) to VoxitNL 2026-06-10 13:26:57 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
BetaBreak/voxit-project#65
No description provided.