Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Workspace PATH being modified on Debian#20199

Unanswered
xiphoid24 asked this question inGeneral
Discussion options

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 thebootstrap 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 ondebian:bookworm anddebian:trixie

$echo$PATH/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

When starting a workspace using an image based ondebian:bookworm anddebian:trixie

$echo$PATH/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games

Note 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 onubuntu:22.04 andubuntu:latest

$echo$PATH/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

When starting a workspace using an image based onubuntu:22.04 andubuntu:latest

$echo$PATH/tmp/coder-script-data/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/home/coder/.coder

I 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

You must be logged in to vote

Replies: 0 comments

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Labels
None yet
1 participant
@xiphoid24

[8]ページ先頭

©2009-2025 Movatter.jp