Environment setup failed: mise error installing rustup

Coding with ChatGPT
,
1

I’ve been usign Codex extensively (love it!) but as of today, about 4 hours ago, my environment fails to start for any and all tasks, so Codex is useless to me today.

Environment setup failed
Script failed: Script exited with code 1

The error reported in the log is:

mise ERROR Tool not installed for shim: rustup
Missing tool version: core:rust@stable
Install all missing tools with: mise install
mise ERROR Run with --verbose or MISE_VERBOSE=1 for more information

As you may have guessed, my environment tries to use rustup. The first line of env setup script is: rustup component add rustfmt. Now, this environment was working fine, but suddenly it seems like rust isn’t available.

Naturally I go the the environment to check what’s up, and I find that the interactive terminal won’t start, with: Terminal errored An unexpected error occurred just as described in the thread “Interactive terminal for Codex environment fails to start”, and I see people are posting there that their terminal is also broken.

Anyone any thoughts or advice? Is there a chance the team pushed an update that is affecting the mise config so that rust isn’t available?

2

Hi @jmsfltchr, can you DM me a task ID for which you are seeing this problem, and ill try to look into it. Thank you!

1 Like
3

Can’t DM here yet due to new account, but you have linkedin mail :joy:

4

I’m now up and running with codex again. Here are my findings:

  • There was an update from the codex team which was causing failures but now seems to be patched
  • In the meantime, rust 1.88.0 got released, which is not supported in the codex containers. In my case I had a rust-toolchain.toml with:
[toolchain]
channel = "stable"

Which tried to use rust 1.88 in the container. The fact that this coincided temporally with the mise error made it look like the issues with Codex weren’t fixed.
Changed toolchain to:

[toolchain]
channel = "1.87.0"

to be compatible with Codex’s Universal container

  • I think something else has materially changed in the config of containers because with an unchanged setup script, and the in-repo change above, my containers would fail to start. I removed some offending commands, which has got Codex working again for me. I haven’t had time to debug this further.

If you’re reading this because you’re having issues, I suggest a cheeky line-by-line audit of your previously working container setup script with the knowledge that something in the env changed.

1 Like