Open tobybellwood opened 6 days ago
@tobybellwood Lando maps the host user's uid/gid onto the container user, see https://github.com/lando/core/blob/main/scripts/user-perms.sh#L94 and the associated helper . Typically that should mean uid/gid is 501 on a Mac.
My guess is that, in this case, the /tmp/ready
file is being created before that mapping occurs.
@pirog you have any suggestions on how to sidestep this issue on Lando 3 services?
You can see here, in this example that the /tmp/ready file (part of the lagoon entrypoints has been created by the solr user (uid:8983 and gid:8983) - but by the time the pod is running, the solr user is now 1000:1000 - and no longer has access to the file/folders created in the entrypoint/startup.
This means that any subsequent lando restarts fail at the entrypoint not being writable by the new solr user. Even when the entrypoint is bypassed (by run_as_root rm /tmp/ready) solr failed to start because of folder access permissions.
Do you have any idea why this uid/gid rewriting is being done - is there some lando-ism I'm missing?
I've also replicated this in our varnish example - as this is another service that uses a named user