Stop using the root user for test/cli containers

[acbramley]

Locally, when running cli/test containers the user that is used is root. This means when running things like config export, or composer install from inside the container (which is required when your host uses a different PHP version since govcms is currently constrained to PHP 8.1) all files resulting from the commands are owned by root:root this then locks them out from being editable from your host (i.e in an IDE)

This leads to a very frustrating experience where multiple times a day I'm having to chown directories on my host machine just to make changes.

Skpr images for example use a skpr user https://github.com/skpr/image-php/blob/main/cli/Dockerfile#L50

This user uses uid and gid of 1000 to align them with linux users

[acbramley]

https://github.com/skpr/image-php/blob/main/base/Dockerfile#L15

[steveworley]

Hey @acbramley — given the constraints with our base images, which create system configuration files through their entrypoints, running the container as a different user is not supported at this time

The best approach to make this workflow more manageable would be to create an ahoy command that would automate the export and chown for you.

# custom/ahoy.yml

commands:
  config:export: |
    docker compose exec cli drush config:export
    chown -R ${UID}:${GID} config/sync

[acbramley]

Confirming this is still an issue. It's also not just config export. Running composer update has the same effect, requiring a chown across core, contrib, libraries, etc.