docker user after upgrade to version 3.6.0 not working #2199
Answered
by
code-asher
kimpenhaus
asked this question in
Q&A
Replies: 1 comment 2 replies
-
Ah yeah looks like `whoami` errors for any ID that isn't already in the
Docker container.
I'm not sure what the proper fix will be yet (maybe we can explicitly
export `USER` as `coder` in the Dockerfile and avoid `whoami`) but one
workaround could be to override the entrypoint and skip all the user
renaming code. For example:
```
docker run -u 1031:100 \
--entrypoint /bin/bash \
codercom/code-server \
-c 'dumb-init fixuid -q /usr/bin/code-server'
```
|
Beta Was this translation helpful? Give feedback.
2 replies
Answer selected by
kimpenhaus
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
hi all,
i am running code-server inside a docker on a synology nas. the container was running flawless - but after upgrading to v3.6.0 it stopped booting properly. I think this is depending on the change mentioned in the release notes:
I've updated my docker create command accordingly (at least accordingly what I understood from the install.md)
user-uid, user-god and user-name are correct:
docker runs as
su
on the synology but the docker should be mapped to a restrictedapps
user - which was working before the upgrade. only change I did was adding-e DOCKER_USER=apps
. that's why it is hardcoded to1031:100
and not to$(id -u):$(id -g)
maybe I misunderstood what to change after the upgrade. but with the given setup the logs are showing:
whoami: cannot find name for user ID 1031
any help is appreciated - thanks!
m.
Beta Was this translation helpful? Give feedback.
All reactions