Closed gpelouze closed 2 months ago
When $BASE_IMAGE_TAGS_URL is not defined, we fall back to https://github.com/QCDIS/NaaVRE-flavors/releases/latest/download/base_image_tags.json in jupyterlab_vre/component_containerizer/handlers.py#L263.
$BASE_IMAGE_TAGS_URL
However, when creating a new release on NaaVRE-flavors, there is a ~45-minutes window during which https://github.com/QCDIS/NaaVRE-flavors/releases/latest/download/base_image_tags.json points to an empty document. When creating a release, we do:
Possible solutions:
BASE_IMAGE_TAGS_URL
We always set BASE_IMAGE_TAGS_URL in deployments to point it to a specific version eg. https://github.com/QCDIS/NaaVRE-flavors/releases/download/v0.14/base_image_tags.json
When
$BASE_IMAGE_TAGS_URL
is not defined, we fall back to https://github.com/QCDIS/NaaVRE-flavors/releases/latest/download/base_image_tags.json in jupyterlab_vre/component_containerizer/handlers.py#L263.However, when creating a new release on NaaVRE-flavors, there is a ~45-minutes window during which https://github.com/QCDIS/NaaVRE-flavors/releases/latest/download/base_image_tags.json points to an empty document. When creating a release, we do:
Possible solutions:
BASE_IMAGE_TAGS_URL
in deployments