https://www.runatlantis.io/ logo
Join Slack
Powered by
Is the reason this says `100` that 100 is the uid ...
# atlantis-community
l
Is the reason this says 
100
that 100 is the uid on alpine? https://github.com/runatlantis/helm-charts/blob/main/charts/atlantis/values.yaml#L300 If you're running as debian, you probably want to set this to 
1000
right?
Copy code
atlantis % docker run -t <http://ghcr.io/runatlantis/atlantis:v0.27.3-alpine|ghcr.io/runatlantis/atlantis:v0.27.3-alpine> id 
No files found in /docker-entrypoint.d/, skipping
uid=100(atlantis) gid=1000(atlantis) groups=1000(atlantis)
vs
Copy code
atlantis % docker run -t <http://ghcr.io/runatlantis/atlantis:v0.27.3-debian|ghcr.io/runatlantis/atlantis:v0.27.3-debian> id 
No files found in /docker-entrypoint.d/, skipping
uid=1000(atlantis) gid=1000(atlantis) groups=1000(atlantis)
I vaguely remember someone saying this is an unfortunate but historical fact that these values are different
p
historical reasons
it has always been that way
l
Any objection w me adding a comment above 
runAsUser
that says something like:
This is to run as the user created within docker 
atlantis
. On alpine that user had uid 
100
, whereas on debian the user has 
1000
.
Since I think we probably expect people to run as the "atlantis" user (whatever that is) ?
Ideally it'd be 
runAsUser: atlantis
and have it do the reverse lookup inside the container but I think it needs a number 🙂
g
There is a PR setting both to 100, but also leaving 1000 on Debian to ensure we don’t break anything.
l
I only noticed because we are using the helm chart which uses uid 100 and gid 1000 (which corresponds to uid/gid on alpine). On debian, atlantis is 1000:1000. So we were relying on the fact that we were in atlantis's group, but not actually running as atlantis. A recent change changed the write permissions of /home/atlantis from 775 to 755, meaning members of the group no longer had permission to write to it and we failed to startup 🙂
I think 755 is more correct than 775 so I'm fine w the change, it just took a bit to realize what's going on
I'm not sure what a good solution here is, since any change from where we are has the potential to break people. Which is why I suggested a comment in the helm chart, which in fairness I might have missed as well 🙂
g
This would fix it for new users while making sure it still works for old users.
l
Ah yeah that solution makes sense to me
2 Views
Open in Slack
PreviousNext
Powered by