Pin a devcontainer version to workaround library search path issue #699
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A new base devcontainer image was released recently that introduces the following error in our environment when running
make test
:A simplified reproduction involves running
conda run -n mlos pytest mlos_bench/mlos_bench/launcher_run_test.ph
.Unfortunately, it appears that under the latest version somewhere between
conda
andpytest
thelibc.so.6
library found is the one under/usr/lib
instead of/opt/conda/envs/mlos/lib
.I haven't quite seen where that's happening, but I've confirmed that rolling back to the previous release for the base devcontainer image fixes it.
Note that even then, we update
conda
to the latest and no-cache update our own dependencies nightly, so we are getting the latest conda at least, if not the latest Debian base packages.This will be somewhat of a security issue eventually, but for now it frees up our CI pipeline to get moving again.