Fix: Update ruby base image to bullseye in CI tests #765
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Sonu Saha <[email protected]>
sean-simmons-progress
approved these changes
Mar 27, 2024
Vasu1105
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
The current Docker image version (ruby:3.1) encounters a ThreadError due to restrictions imposed by libseccomp, blocking certain system calls necessary for the certain operations.
This PR addresses the issue encountered in the current Docker image setup by updating the Docker image version from ruby:3.1 to ruby:3.1-bullseye.
Note: This is a workaround
Related Issue
CHEF-11234: CI is breaking for inspec, inspec-gcp, and train due to issue with docker image used for the tests
Types of changes
Checklist: