Skip to content
Docker CI (v1 + v2)

perf: optimize CI workflow and Dockerfiles for faster builds #87

Sign in to view logs

perf: optimize CI workflow and Dockerfiles for faster builds

perf: optimize CI workflow and Dockerfiles for faster builds #87

Triggered via pull request March 26, 2026 20:57
@KingPinKingPin
opened #31
ci-optimizations
Status Success
Total duration 11m 37s
Artifacts 23

docker-ci.yml

on: pull_request
setup
3s
setup
Matrix: build-and-test
Matrix: publish
Fit to window
Zoom out
Zoom in

Annotations

23 warnings and 24 notices
v1-8.2-apache-bookworm
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
v1-8.4-apache-bookworm
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
v1-8.4-cli-bookworm
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
v1-8.4-fpm-alpine
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
v1-8.2-cli-bookworm
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
v1-8.2-fpm-alpine
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
v1-8.2-fpm-bookworm
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
v2-8.2-apache-trixie
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
v1-8.2-cli-alpine
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
v2-8.3-cli-trixie
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
v1-8.4-cli-alpine
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
v1-8.4-fpm-bookworm
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
v2-8.4-cli-trixie
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
v2-8.2-cli-alpine
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
v2-8.4-cli-alpine
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
v2-8.3-fpm-trixie
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
v2-8.2-cli-trixie
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
v2-8.2-fpm-alpine
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
v2-8.4-fpm-alpine
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
v2-8.4-apache-trixie
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
v2-8.2-fpm-trixie
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
v2-8.3-apache-trixie
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
v2-8.4-fpm-trixie
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
setup
PR detected — testing PHP 8.4 + 8.2 only (skipping 8.3)
v1-8.2-apache-bookworm
✅ Build and tests passed for v1 - php-docker:8.2-apache-bookworm
v1-8.4-apache-bookworm
✅ Build and tests passed for v1 - php-docker:8.4-apache-bookworm
v1-8.4-cli-bookworm
✅ Build and tests passed for v1 - php-docker:8.4-cli-bookworm
v1-8.4-fpm-alpine
✅ Build and tests passed for v1 - php-docker:8.4-fpm-alpine
v1-8.2-cli-bookworm
✅ Build and tests passed for v1 - php-docker:8.2-cli-bookworm
v1-8.2-fpm-alpine
✅ Build and tests passed for v1 - php-docker:8.2-fpm-alpine
v1-8.2-fpm-bookworm
✅ Build and tests passed for v1 - php-docker:8.2-fpm-bookworm
v2-8.2-apache-trixie
✅ Build and tests passed for v2 - php-docker:8.2-apache-trixie-v2
v1-8.2-cli-alpine
✅ Build and tests passed for v1 - php-docker:8.2-cli-alpine
v2-8.3-cli-trixie
✅ Build and tests passed for v2 - php-docker:8.3-cli-trixie-v2
v1-8.4-cli-alpine
✅ Build and tests passed for v1 - php-docker:8.4-cli-alpine
v1-8.4-fpm-bookworm
✅ Build and tests passed for v1 - php-docker:8.4-fpm-bookworm
v2-8.4-cli-trixie
✅ Build and tests passed for v2 - php-docker:8.4-cli-trixie-v2
v2-8.2-cli-alpine
✅ Build and tests passed for v2 - php-docker:8.2-cli-alpine-v2
v2-8.4-cli-alpine
✅ Build and tests passed for v2 - php-docker:8.4-cli-alpine-v2
v2-8.3-fpm-trixie
✅ Build and tests passed for v2 - php-docker:8.3-fpm-trixie-v2
v2-8.2-cli-trixie
✅ Build and tests passed for v2 - php-docker:8.2-cli-trixie-v2
v2-8.2-fpm-alpine
✅ Build and tests passed for v2 - php-docker:8.2-fpm-alpine-v2
v2-8.4-fpm-alpine
✅ Build and tests passed for v2 - php-docker:8.4-fpm-alpine-v2
v2-8.4-apache-trixie
✅ Build and tests passed for v2 - php-docker:8.4-apache-trixie-v2
v2-8.2-fpm-trixie
✅ Build and tests passed for v2 - php-docker:8.2-fpm-trixie-v2
v2-8.3-apache-trixie
✅ Build and tests passed for v2 - php-docker:8.3-apache-trixie-v2
v2-8.4-fpm-trixie
✅ Build and tests passed for v2 - php-docker:8.4-fpm-trixie-v2

Artifacts

Produced during runtime
Name Size Digest
KingPin~php-docker~19C9C2.dockerbuild Expired
263 KB
sha256:085b40876b4b3da3b2c63509e3d6185da134075d42be04a203a2955542f2d7cb
KingPin~php-docker~26QCTO.dockerbuild Expired
322 KB
sha256:44bda70fae8d17091ef38e70de2f9dae91f18811b5411d1ebcd2dd5d97397769
KingPin~php-docker~2X0QAK.dockerbuild Expired
291 KB
sha256:7be980b7e2d6e1077bf8f5c1b86f7a353fc75e955563614280705ec48fb7a1c2
KingPin~php-docker~67VDK6.dockerbuild Expired
248 KB
sha256:e98dba0aa9c04c3161ed6ca6416b4cd62c6d8d3c831aa12b02535b93e6aca333
KingPin~php-docker~830VUO.dockerbuild Expired
291 KB
sha256:d30592dd3f8a390dc2f3b76bf1ea3a1c52ef17257e7cf5b025dc3ab0bbd8ab48
KingPin~php-docker~8SJ3UL.dockerbuild Expired
310 KB
sha256:4ec81a41019e0caebfae96259614cf90f4c04a224e10c2b714815ab68d706cd4
KingPin~php-docker~AAD8QU.dockerbuild Expired
311 KB
sha256:993d95ca3f99a6b482db8ac76be4b64953f8381c2fed4956fdfe1a029977e63f
KingPin~php-docker~AJBZ0R.dockerbuild Expired
283 KB
sha256:b090936d99050e288e542493804e72616e059ac495d8d13e94a5dff464cbb3a5
KingPin~php-docker~I0QT51.dockerbuild Expired
248 KB
sha256:8477531896bb026f115edcc608d813474644435f1787ed2187a6a716605ca990
KingPin~php-docker~ICX6AC.dockerbuild Expired
248 KB
sha256:0e80900e35d92f82a2af6b22a626f726ca3746c9d2beeeedafeb65d90a7aa18d
KingPin~php-docker~JD145F.dockerbuild Expired
266 KB
sha256:61241a3163f73d4a0fbcf655d1103e8e99ec24dcf6a6ba74c08679a744a7898a
KingPin~php-docker~K0QVID.dockerbuild Expired
316 KB
sha256:35840928729e5fd0002f79e93bbb23f9fa4076016a69eb16d387ec32e9f7700e
KingPin~php-docker~K8KWD3.dockerbuild Expired
313 KB
sha256:12c3e83e22af350fd898b8326ebb6c945cce4b0c1aeb4a3ae583c37bae9b2fc7
KingPin~php-docker~LABJ02.dockerbuild Expired
319 KB
sha256:f5e4f976888c60a11c77d4037131e17a86b4aed05293322894f57b26c224aa54
KingPin~php-docker~SZIWPN.dockerbuild Expired
270 KB
sha256:fd70c22068f337bc37b1160d71fefee1b7fbfa5878fd8cc7d886a4a9dadf3615
KingPin~php-docker~TOJAQB.dockerbuild Expired
284 KB
sha256:ef141cebdb86f21849228243e3450b99aea60bf16f24145f795f81c5a4e7b09f
KingPin~php-docker~TR4UXD.dockerbuild Expired
295 KB
sha256:a9ee41e25f1f9aea9ccadd0822dd6c33ac4974df61c4a28d4f7fda88cacf29d3
KingPin~php-docker~UHM82Q.dockerbuild Expired
249 KB
sha256:c633684163e635d260c1594c3da381a43d8ee5d6e73f2790e17e51e0aa7d51ff
KingPin~php-docker~V8PKIZ.dockerbuild Expired
310 KB
sha256:e683229f4c3f0c77b362c60acbea964462f4e72aaacb6a12154b40c4e973853b
KingPin~php-docker~VI59NC.dockerbuild Expired
313 KB
sha256:27dc6fd64e468b453cf2250a7f16e957136c9d2728a084800eadfe8f2c562712
KingPin~php-docker~WGN4CS.dockerbuild Expired
317 KB
sha256:7ddca8ed8dba5e65c0c6451a9970650f38775c2d6fa5dbefea815400acb6ab6b
KingPin~php-docker~Z8O7LX.dockerbuild Expired
261 KB
sha256:a31f723f3fb0e932d3be276fdc27c6a7a69ca580d244031993432b431a5e48f2
KingPin~php-docker~ZIVLZX.dockerbuild Expired
277 KB
sha256:51472da246d811e185e38432a2b7df164372bb8a5c898cf9cd39d7d7fbfefefe