-
|
We have a few workspace templates that can use different images depending on what the workspace needs to do. When I create a workspace using the Debian based image I created, the PATH is modified in a way that I would not expect. This modification only happens when the image is used to create a workspace. We are using K8s with envbox for the workspaces but I was also able to recreate this with just a K8s deploy (no envbox). When I run a docker container using the image the PATH is what I would expect. I was able to find the bootstrap script that I think is being run but I don't see any direct PATH modifications there. When starting a docker container using an image based on $ echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/binWhen starting a workspace using an image based on $ echo $PATH
/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/gamesNote the addition of the games paths and no reference to coder directories I used the same Dockerfile but changed the initial FROM to be ubuntu and I am not seeing this issue When starting a docker container using an image based on $ echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/binWhen starting a workspace using an image based on $ echo $PATH
/tmp/coder-script-data/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/home/coder/.coderI have stripped down the Dockerfile to what I believe to only be the minimum needed to create a workspace to eliminate any extra packages being the root cause. Are there any packages that could be missing from the base Debian image that Coder uses during provisioning that might cause this? Could the Debian base image contain extra packages that might be causing a conflict with the Coder provisioning? I assume it is something on my end that may be causing this but I have been rebuilding and testing new images for awhile and I am a bit stuck. I would appreciate any insight or help with this issue. I can provide the Dockerfile I am using if needed |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
This turned out to be with the Debian Dockerfile. In if [ "$(id -u)" -eq 0 ]; then
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
else
PATH="/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games"
fi
export PATHIt seems the way I was starting the docker container locally was not considering it as an interactive terminal so |
Beta Was this translation helpful? Give feedback.
This turned out to be with the Debian Dockerfile. In
/etc/profilethere is a check for the user which will overwrite thePATH.It seems the way I was starting the docker container locally was not considering it as an interactive terminal so
/etc/profilewas not being loaded and in turn I was unable to replicate this behavior. I was able to update the Dockerfile that uses Debian to have an alternate/etc/profileand it is working now