Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update asciidoctor-spec image to ruby:3.3.3 #40

Merged
merged 1 commit into from
Jul 2, 2024
Merged

Conversation

oddhack
Copy link
Collaborator

@oddhack oddhack commented Jul 1, 2024

This greatly reduces the number of CVEs reported by Dockerhub and also updates the toolchain to current versions of asciidoctor (which apparently gives some better error messages now than it used to).

Because of the underlying Debian updates, Python packages can no longer be installed at system level without a very ugly and brute-force override. Instead this image sets up a Python virtual environment containing all the packages, with just enough of an OS-level Python to install venv itself. If you are following the image instructions to do your own non-Docker install of the toolchain, you will need to setup a venv and then use the 'activate' script or otherwise setup your VIRTUAL_ENV and PATH to use that version. Scripts relying on Python packages installed by this image must invoke the python3 in the venv, not /usr/bin/python3.

This greatly reduces the number of CVEs reported by Dockerhub and also
updates the toolchain to current versions of asciidoctor (which
apparently gives some better error messages now than it used to).

Because of the underlying Debian updates, Python packages can no longer
be installed at system level without a very ugly and brute-force
override. Instead this image sets up a Python virtual environment
containing all the packages, with just enough of an OS-level Python to
install venv itself. If you are following the image instructions to do
your own non-Docker install of the toolchain, you will need to setup a
venv and then use the 'activate' script or otherwise setup your
VIRTUAL_ENV and PATH to use that version. Scripts relying on Python
packages installed by this image must invoke the python3 in the venv,
not /usr/bin/python3.
@oddhack
Copy link
Collaborator Author

oddhack commented Jul 1, 2024

@rpavlik headsup for you if updating to a newer base image about the Debian / Python system package install restriction change, that might affect your Dockerfiles as well.

@oddhack
Copy link
Collaborator Author

oddhack commented Jul 2, 2024

SYCL has KhronosGroup/SYCL-Docs#576 queued up to use the updated image and migrate to specifying by SHA instead of just by name, and I have a comparable internal MR that will go out soon for Vulkan-Docs and have verified Actions works with the image, so calling this good.

@oddhack oddhack merged commit dcaf30f into main Jul 2, 2024
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant