-
-
Notifications
You must be signed in to change notification settings - Fork 289
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] command not found: poetry
with mod code-server-python3-poetry
#977
Comments
It seems that only the alias is missing, since running With the selection of mods I've used, here are - from the container cmd - the # DOCKER_MODS=linuxserver/mods:code-server-python3-poetry|linuxserver/mods:universal-docker|
# linuxserver/mods:code-server-pnpm|linuxserver/mods:code-server-nodejs|linuxserver/mods:code-server-zsh|
# linuxserver/mods:code-server-nvm
# tested echo $PATH && printenv PATH && env | /bin/grep PATH
> echo $PATH
/config/.nvm/versions/node/v23.2.0/bin:/config/.local/share/pnpm:/lsiopy/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
> cat /var/run/s6/container_environment/PATH
/command:/lsiopy/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:$HOME/.local/binroot
# Note zsh, nodejs have been added directly to /usr/bin/ so only poetry is missing What's weird is that from code-server terminal poetry should be accessible since > $ echo $PATH
/app/code-server/lib/vscode/bin/remote-cli:/config/.nvm/versions/node/v23.2.0/bin:/config/.local/share/pnpm:
/command:/lsiopy/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:$HOME/.local/bin
> $ ls $HOME/.local/bin
poetry
> $ $HOME/.local/bin/poetry --version
Poetry (version 1.8.4)
> $ poetry --version
bash: poetry: command not found Looking at the PR and how path is handled below, it seems that this is done differently in poetry than eg See alternatives way to set path
The issue might however come from another docker-mod that erases poetry but not the other due to the order of the modules being loaded - will try to pinpoint which one with more testing. |
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
Hi there, the issue is still present, please don't mark it as stale. Hope to find a fix! |
@jo-chemla Hi! Apologies for not getting back to you, I have not been able to replicate this error... Here's the docker compose I have for you to compare:
@aptalca what are your thoughts on setting the path for poetry? |
Thanks for getting back. I dug a bit more into the logs, and indeed It might indeed be useful that the
|
Thanks for the PR #989 ! I just did another try at pulling the code-server image and spinning up the container, using the poetry docker-mod, but still face the error Probably once the PR commits gets merged into the mod branch, one need to wait for a new release of the mod? From the docker-hub registry of linuxserver/mods, a new release followed the merged PR here yet it seems either I'm not fetching it or the fix won't make poetry available in PATH. Thanks again for your help! EDIT: |
Is there an existing issue for this?
Name of mod
code-server-python3-poetry
Name of base container
lscr.io/linuxserver/code-server
Current Behavior
I tried the recent #958
code-server-python3-poetry
dockermod by @howardt12345 but it seems that poetry is not installed in my setup, since running the following command either in container or code-server console returns:command not found: poetry
Running
python3
does succeed.I also tried restarting the container or re-running compose multiple times, but poetry is never found in path. The whole logs are in the dedicated section, below is the section regarding poetry.
Expected Behavior
According to #959 running
poetry --version
should succeed in returning poetry version numberSteps To Reproduce
poetry --version
command not found: poetry
.Environment
CPU architecture
x86-64
Docker creation
Container logs
Full logs
The text was updated successfully, but these errors were encountered: