osmith has uploaded this change for review.
fix_perms: use debian:bullseye
Use debian:bullseye instead of debian-bullseye-build. Building the
latter requires a lot of time, it's definitively not needed for just
running chmod. Use debian:bullseye, since we use it as base for most
images and it's therefore very likely that it's already downloaded
(and if not, it would get downloaded here).
Change-Id: I88f513a0a8ee04628842a7aa1b663c390d2032cd
---
M jenkins-common.sh
1 file changed, 1 insertion(+), 5 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/docker-playground refs/changes/03/28903/1
diff --git a/jenkins-common.sh b/jenkins-common.sh
index 830c65c..f12bdf0 100644
--- a/jenkins-common.sh
+++ b/jenkins-common.sh
@@ -245,16 +245,12 @@
}
fix_perms() {
- if ! docker_image_exists "debian-bullseye-build"; then
- docker_images_require "debian-bullseye-build"
- fi
-
echo Fixing permissions
docker run --rm \
-v $VOL_BASE_DIR:/data \
-v $CACHE_DIR:/cache \
--name ${BUILD_TAG}-cleaner \
- $REPO_USER/debian-bullseye-build \
+ debian:bullseye \
chmod -R a+rX /data/ /cache/
}
To view, visit change 28903. To unsubscribe, or for help writing mail filters, visit settings.