In our Codex environment, we’re unable to use Bun.
Our project holds a .bun-version file that contains “v1.2.19”.
I see in the Codex container image’s pre-installed packages that Bun v1.2.14 is available.
During setup, I see the following:
mise WARN missing: bun@v1.2.19
→ rm -- /tmp/CLYbX1-setup_script.sh
→ set +x
→ bun install
/tmp/CLYbX1-setup_script.sh: line 5: bun: command not found
It appears to be related to mise:
# This works
mise exec bun@1.2.14 -- bun install
# This does NOT work
mise use [--global] bun@1.2.14 # with or without --global
bun install
Edit: Though this allows the environment to be set up, Codex still tries to run bun test when developing, which fails.
Does anyone know how I can support simply using the bun command in my Codex environment?
1 Like
ttarik
2
I’m seeing the same with Ruby in a project which has a .ruby-version.
It was working fine until about a week ago.
Now the setup script fails with command not found whenever trying to use ruby or things like bundle/gem.
If I comment out those lines and run the environment terminal, the commands do work in the terminal. They just stopped working in the setup script.
We used to be able to use bun on our end, too. I can’t quite tell when it failed, but it was only in the last month sometime.
vb
4
Hi and welcome to the community!
Have you seen the other bun related topic? They did find some creative solutions to manage and maybe you can use them as well?
Also, there is this related topic to the mise issue
I hope this helps a little bit.