You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Docker container fails to start due to bun dependency install issue #4774
changed the title [-]Docker container fails on dependency pull[/-][+]Docker container fails to start due to bun dependency install issue[/+]on Nov 26, 2025
It's very peculiar. On my desktop it works 100% of the time, on my laptop (ThinkPad P14s Gen2, AMD variant) it works 0% of the time, always the same error. Same Fedora 43 on Wayland, same Terminator terminal, sitting on the same desk connected to the same wired LAN.
What does work on both is docker run -it --rm ghcr.io/sst/opencode --help - the help screen is shown alright, it's just when the TUi is about to start that it gets problematic.
Ig as a workaround you can pass: OPENCODE_DISABLE_DEFAULT_PLUGINS=true downside is you won't be able to use github copilot oauth or anthropic oauth but everything else should still work
I identified 2 separate causes of issues on my work laptop:
I use a nonstandard UID and GID for work -> when actually mounting something into the container, I had permission issues left and right... desktop is the usual 1000:1000 so not nearly as many issues there
for company needs I have an internal DNS server preset in my docker daemon config, that was resolved by providing nameserver by hand
I've worked around these issues and now I can code in docker alright.
BTW, OpenCode seems to expect ripgrep, but it's not available in the official container image.
No, not even on the desktop where I have no issues, using the default Big Pickle model with the official image.
The documentation recommends docker run -it --rm ghcr.io/sst/opencode, so even if rg got installed, it will be lost immediately after quitting the container.
Sorry for going off-topic; I have solved my local root causes and from my perspective this issue can be closed.
Activity
[-]Docker container fails on dependency pull[/-][+]Docker container fails to start due to bun dependency install issue[/+]github-actions commentedon Nov 26, 2025
This issue might be a duplicate of existing issues. Please check:
Feel free to ignore if none of these address your specific case.
rekram1-node commentedon Nov 26, 2025
Does that happen everytime for u? Or is it intermittent
Nindaleth commentedon Nov 26, 2025
It's very peculiar. On my desktop it works 100% of the time, on my laptop (ThinkPad P14s Gen2, AMD variant) it works 0% of the time, always the same error. Same Fedora 43 on Wayland, same Terminator terminal, sitting on the same desk connected to the same wired LAN.
What does work on both is
docker run -it --rm ghcr.io/sst/opencode --help- the help screen is shown alright, it's just when the TUi is about to start that it gets problematic.Nindaleth commentedon Nov 26, 2025
Here's a log I was able to extract from the docker container:
2025-11-26T220647.log
rekram1-node commentedon Nov 26, 2025
Ig as a workaround you can pass:
OPENCODE_DISABLE_DEFAULT_PLUGINS=truedownside is you won't be able to use github copilot oauth or anthropic oauth but everything else should still workNindaleth commentedon Nov 27, 2025
Thanks! This still hangs for about 15 seconds on start, but then runs, that sounds good for now.
Nindaleth commentedon Dec 1, 2025
I identified 2 separate causes of issues on my work laptop:
I've worked around these issues and now I can code in docker alright.
BTW, OpenCode seems to expect ripgrep, but it's not available in the official container image.
rekram1-node commentedon Dec 1, 2025
We automatically install it if it isn't available but I guess that isn't working for you?
Nindaleth commentedon Dec 1, 2025
No, not even on the desktop where I have no issues, using the default Big Pickle model with the official image.
The documentation recommends
docker run -it --rm ghcr.io/sst/opencode, so even ifrggot installed, it will be lost immediately after quitting the container.Sorry for going off-topic; I have solved my local root causes and from my perspective this issue can be closed.
rekram1-node commentedon Dec 1, 2025
ah I see, yeah we will prolly want to bundle it in automatically