Describe the bug

The cargo build command after the devcontainer starts with the following error:

error: failed to parse lock file at: /workspaces/redlib/Cargo.lock

Caused by:
  lock file version `4` was found, but this version of Cargo does not understand this lock file, perhaps Cargo needs to be updated?

Steps to reproduce the bug

1. clone the repository
2. open it with Visual Studio Code
3. open the command palette
4. run the Dev Containers: Reopen in Container command
5. wait for container to build and notice the error

What's the expected behavior?

The postCreateCommand should execute inside the devcontainer right away without failing

Additional context / screenshot

Updating the base image to mcr.microsoft.com/devcontainers/rust:1.0.23-bookworm fixes this issue.
I'm available to open a Pull Request with this change.

• I checked that the instance that this was reported on is running the latest git commit, or I can reproduce it locally on the latest git commit