Zitadel Docker Compose example with Service Account fails to load
Original message was deleted
EI think the example is broken. @stebenz would you mind having a look?
S@ehoodkatz yes, I took a look, the version of the ZITADEL image is the problem, will correct it immediately, but if you change "image: 'ghcr.io/zitadel/zitadel:stable'" with "image: 'ghcr.io/zitadel/zitadel:latest'" it works
problem is that the stable version can't marshal the extended yaml
problem is that the stable version can't marshal the extended yaml
S@ehoodkatz the /zitadel-admin-sa.json is the service account key which is written during the setup, i guess that the local path you used for docker is so that you have no permission in the container to write the key on the path, this key can then be used to connect to the API
Smaybe there is a difference on how it handels locally
first off, I guess you mean at setup not at startup right? as startup is everytime zitadel would restart
second, unfortunately this function is exactly used for this situation, to create the first user as a machine user so that you can directly connect to the API.
did you try to mount an existing folder into docker? the problem should be that the zitadel-user of the container has no permission to write in the mounted folder
first off, I guess you mean at setup not at startup right? as startup is everytime zitadel would restart
second, unfortunately this function is exactly used for this situation, to create the first user as a machine user so that you can directly connect to the API.
did you try to mount an existing folder into docker? the problem should be that the zitadel-user of the container has no permission to write in the mounted folder
Eon my ubuntu, ensuring, the machinekey directory has the current linux users ownership resolved the issue. @stebenz we could add the commands
mkdir -p machinekey and chown $(id -u):$(id -g) machinekey or similar to the docs? Don't know exactly what the most platform agnostic and idempotent commands are.