Open ugurcancaykara opened 5 months ago
I'm curious where this landed. seems like there was a PR to ensure the directory exists, but was closed because an alternate resolution was found. I tried searching through the atlantis codebase and cannot find any references to sshd
anywhere.
ok, think I've found the issue. the wrong uid is being used during operation. we've been hard-coding the runtime user to 100:1000
because of this issue, and I guess AWS ECS was assigning 100
to the /run/sshd
user. as a workaround, we essentially did something more or less equivalent to this PR:
atlantis
user to 1000
chown
its home directory to 1000:1000
1000:1000
the PR I mentioned would probably do away for the need of this workaround.
Community Note
Overview of the Issue
When using the alpine based image
ghcr.io/runatlantis/atlantis:v0.27.1
write git-credentials succeed with the following message:but when using the debian based image
ghcr.io/runatlantis/atlantis:v0.27.1-debian
write git-credentials failed with the following message:Reproduction Steps
Switch image tag from
v0.27.1
tov0.27.1-debian
Environment details
Atlantis server-side config file:
Repo
atlantis.yaml
file: Note: terragrunt is unused