chore: update Node.js and Maven versions in Dockerfile and versions.j… #11
danbaoAnnotations
15 errors and 16 warnings
|
build (node22-jdk25, 22.22.2, 22, 25, 3.9.15-jdk25.0.2-noble, false)
buildx failed with: ERROR: failed to build: failed to solve: ghcr.io/ringcentral-docker/maven:3.9.15-jdk25.0.2-noble: failed to resolve source metadata for ghcr.io/ringcentral-docker/maven:3.9.15-jdk25.0.2-noble: ghcr.io/ringcentral-docker/maven:3.9.15-jdk25.0.2-noble: not found
|
|
build (node22-jdk17, 22.22.2, 22, 17, 3.9.15-jdk17.0.18-noble, false)
buildx failed with: ERROR: failed to build: failed to solve: ghcr.io/ringcentral-docker/maven:3.9.15-jdk17.0.18-noble: failed to resolve source metadata for ghcr.io/ringcentral-docker/maven:3.9.15-jdk17.0.18-noble: ghcr.io/ringcentral-docker/maven:3.9.15-jdk17.0.18-noble: not found
|
|
build (node20-jdk21, 20.20.2, 20, 21, 3.9.15-jdk21.0.10-noble, false)
buildx failed with: ERROR: failed to build: failed to solve: ghcr.io/ringcentral-docker/maven:3.9.15-jdk21.0.10-noble: failed to resolve source metadata for ghcr.io/ringcentral-docker/maven:3.9.15-jdk21.0.10-noble: ghcr.io/ringcentral-docker/maven:3.9.15-jdk21.0.10-noble: not found
|
|
build (node24-jdk21, 24.15.0, 24, 21, 3.9.15-jdk21.0.10-noble, false)
buildx failed with: ERROR: failed to build: failed to solve: ghcr.io/ringcentral-docker/maven:3.9.15-jdk21.0.10-noble: failed to resolve source metadata for ghcr.io/ringcentral-docker/maven:3.9.15-jdk21.0.10-noble: ghcr.io/ringcentral-docker/maven:3.9.15-jdk21.0.10-noble: not found
|
|
build (node24-jdk11, 24.15.0, 24, 11, 3.9.15-jdk11.0.30-noble, false)
buildx failed with: ERROR: failed to build: failed to solve: ghcr.io/ringcentral-docker/maven:3.9.15-jdk11.0.30-noble: failed to resolve source metadata for ghcr.io/ringcentral-docker/maven:3.9.15-jdk11.0.30-noble: ghcr.io/ringcentral-docker/maven:3.9.15-jdk11.0.30-noble: not found
|
|
build (node22-jdk21, 22.22.2, 22, 21, 3.9.15-jdk21.0.10-noble, true)
buildx failed with: ERROR: failed to build: failed to solve: ghcr.io/ringcentral-docker/maven:3.9.15-jdk21.0.10-noble: failed to resolve source metadata for ghcr.io/ringcentral-docker/maven:3.9.15-jdk21.0.10-noble: ghcr.io/ringcentral-docker/maven:3.9.15-jdk21.0.10-noble: not found
|
|
build (node24-jdk17, 24.15.0, 24, 17, 3.9.15-jdk17.0.18-noble, false)
buildx failed with: ERROR: failed to build: failed to solve: ghcr.io/ringcentral-docker/maven:3.9.15-jdk17.0.18-noble: failed to resolve source metadata for ghcr.io/ringcentral-docker/maven:3.9.15-jdk17.0.18-noble: ghcr.io/ringcentral-docker/maven:3.9.15-jdk17.0.18-noble: not found
|
|
build (node24-jdk8, 24.15.0, 24, 8, 3.8.9-jdk8u482-noble, false)
buildx failed with: ERROR: failed to build: failed to solve: ghcr.io/ringcentral-docker/maven:3.8.9-jdk8u482-noble: failed to resolve source metadata for ghcr.io/ringcentral-docker/maven:3.8.9-jdk8u482-noble: ghcr.io/ringcentral-docker/maven:3.8.9-jdk8u482-noble: not found
|
|
build (node22-jdk8, 22.22.2, 22, 8, 3.8.9-jdk8u482-noble, false)
buildx failed with: ERROR: failed to build: failed to solve: ghcr.io/ringcentral-docker/maven:3.8.9-jdk8u482-noble: failed to resolve source metadata for ghcr.io/ringcentral-docker/maven:3.8.9-jdk8u482-noble: ghcr.io/ringcentral-docker/maven:3.8.9-jdk8u482-noble: not found
|
|
build (node20-jdk8, 20.20.2, 20, 8, 3.8.9-jdk8u482-noble, false)
buildx failed with: ERROR: failed to build: failed to solve: ghcr.io/ringcentral-docker/maven:3.8.9-jdk8u482-noble: failed to resolve source metadata for ghcr.io/ringcentral-docker/maven:3.8.9-jdk8u482-noble: ghcr.io/ringcentral-docker/maven:3.8.9-jdk8u482-noble: not found
|
|
build (node20-jdk25, 20.20.2, 20, 25, 3.9.15-jdk25.0.2-noble, false)
buildx failed with: ERROR: failed to build: failed to solve: ghcr.io/ringcentral-docker/maven:3.9.15-jdk25.0.2-noble: failed to resolve source metadata for ghcr.io/ringcentral-docker/maven:3.9.15-jdk25.0.2-noble: ghcr.io/ringcentral-docker/maven:3.9.15-jdk25.0.2-noble: not found
|
|
build (node24-jdk25, 24.15.0, 24, 25, 3.9.15-jdk25.0.2-noble, false)
buildx failed with: ERROR: failed to build: failed to solve: ghcr.io/ringcentral-docker/maven:3.9.15-jdk25.0.2-noble: failed to resolve source metadata for ghcr.io/ringcentral-docker/maven:3.9.15-jdk25.0.2-noble: ghcr.io/ringcentral-docker/maven:3.9.15-jdk25.0.2-noble: not found
|
|
build (node22-jdk11, 22.22.2, 22, 11, 3.9.15-jdk11.0.30-noble, false)
buildx failed with: ERROR: failed to build: failed to solve: ghcr.io/ringcentral-docker/maven:3.9.15-jdk11.0.30-noble: failed to resolve source metadata for ghcr.io/ringcentral-docker/maven:3.9.15-jdk11.0.30-noble: ghcr.io/ringcentral-docker/maven:3.9.15-jdk11.0.30-noble: not found
|
|
build (node20-jdk11, 20.20.2, 20, 11, 3.9.15-jdk11.0.30-noble, false)
buildx failed with: ERROR: failed to build: failed to solve: ghcr.io/ringcentral-docker/maven:3.9.15-jdk11.0.30-noble: failed to resolve source metadata for ghcr.io/ringcentral-docker/maven:3.9.15-jdk11.0.30-noble: ghcr.io/ringcentral-docker/maven:3.9.15-jdk11.0.30-noble: not found
|
|
build (node20-jdk17, 20.20.2, 20, 17, 3.9.15-jdk17.0.18-noble, false)
buildx failed with: ERROR: failed to build: failed to solve: ghcr.io/ringcentral-docker/maven:3.9.15-jdk17.0.18-noble: failed to resolve source metadata for ghcr.io/ringcentral-docker/maven:3.9.15-jdk17.0.18-noble: ghcr.io/ringcentral-docker/maven:3.9.15-jdk17.0.18-noble: not found
|
|
prepare
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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/
|
|
build (node22-jdk25, 22.22.2, 22, 25, 3.9.15-jdk25.0.2-noble, false)
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/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-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/
|
|
build (node22-jdk17, 22.22.2, 22, 17, 3.9.15-jdk17.0.18-noble, false)
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/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-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/
|
|
build (node20-jdk21, 20.20.2, 20, 21, 3.9.15-jdk21.0.10-noble, false)
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/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-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/
|
|
build (node24-jdk21, 24.15.0, 24, 21, 3.9.15-jdk21.0.10-noble, false)
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/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-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/
|
|
build (node24-jdk11, 24.15.0, 24, 11, 3.9.15-jdk11.0.30-noble, false)
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/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-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/
|
|
build (node22-jdk21, 22.22.2, 22, 21, 3.9.15-jdk21.0.10-noble, true)
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/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-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/
|
|
build (node24-jdk17, 24.15.0, 24, 17, 3.9.15-jdk17.0.18-noble, false)
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/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-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/
|
|
build (node24-jdk8, 24.15.0, 24, 8, 3.8.9-jdk8u482-noble, false)
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/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-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/
|
|
build (node22-jdk8, 22.22.2, 22, 8, 3.8.9-jdk8u482-noble, false)
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/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-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/
|
|
build (node20-jdk8, 20.20.2, 20, 8, 3.8.9-jdk8u482-noble, false)
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/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-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/
|
|
build (node20-jdk25, 20.20.2, 20, 25, 3.9.15-jdk25.0.2-noble, false)
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/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-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/
|
|
build (node24-jdk25, 24.15.0, 24, 25, 3.9.15-jdk25.0.2-noble, false)
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/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-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/
|
|
build (node22-jdk11, 22.22.2, 22, 11, 3.9.15-jdk11.0.30-noble, false)
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/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-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/
|
|
build (node20-jdk11, 20.20.2, 20, 11, 3.9.15-jdk11.0.30-noble, false)
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/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-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/
|
|
build (node20-jdk17, 20.20.2, 20, 17, 3.9.15-jdk17.0.18-noble, false)
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/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
ringcentral-docker~node~3H2F3G.dockerbuild
|
15.3 KB |
sha256:69f4138b2d0b34ee82640ee90fa7da0cc6e8ffb5ddcba500f18b56d18f70c940
|
|
|
ringcentral-docker~node~54KQXE.dockerbuild
|
14.8 KB |
sha256:e0c6a4bec90f050693f3dad2058320d40c2ea322094945b3d94b5aeca97ea2cd
|
|
|
ringcentral-docker~node~61GK5Z.dockerbuild
|
14.4 KB |
sha256:895f521cf7e74dd007a0070264b6d89e04e2aaf50a61f03170e45f06e8b17114
|
|
|
ringcentral-docker~node~G55WK0.dockerbuild
|
13.9 KB |
sha256:59a9a553ef44fea872eea3a18f5b0b8ad6a34a621e5d2caa2014e526724cdfca
|
|
|
ringcentral-docker~node~HIDK3A.dockerbuild
|
14.2 KB |
sha256:75f57323bc8a21a55ccd085182da9ae4dc85d39f8ee375805fc1a0abfa4a703f
|
|
|
ringcentral-docker~node~I2M8RW.dockerbuild
|
14.3 KB |
sha256:185f96c2f362206dfe82984141f4e440638a5c8a9689edf89dd952c055fd2ddb
|
|
|
ringcentral-docker~node~IWF5D5.dockerbuild
|
14.7 KB |
sha256:0e6ff36d059b906a685538a78daa6e09a9ffd9314b6091a8fff98aa6dc455167
|
|
|
ringcentral-docker~node~JMLAOY.dockerbuild
|
13.4 KB |
sha256:5395cc8f1872246e1e5b3b0891061eca7542deb0b6d673a5e21232b2b7014501
|
|
|
ringcentral-docker~node~MDZKT6.dockerbuild
|
14.5 KB |
sha256:6c4205f5581f6e5feb3d9ea4e51d184c4f23d05cfb0b9bbb97fe483d0198a504
|
|
|
ringcentral-docker~node~PX0FQQ.dockerbuild
|
14.2 KB |
sha256:3f1b1d1020630ac5a0e3448e6e16c6ef70bf1dc3eabd16ddd1c77780950c145d
|
|
|
ringcentral-docker~node~SQ9J1K.dockerbuild
|
14.8 KB |
sha256:8e305ad3ef38dcccfe89ef3487d001e1725b3ec9bdbf3c357ef8b9a2266c7930
|
|
|
ringcentral-docker~node~TDC5MS.dockerbuild
|
14.2 KB |
sha256:43b7f18690027ed826c2bad165c208dcde98e78b0265109909fb4fabbc8c3ccd
|
|
|
ringcentral-docker~node~V06F49.dockerbuild
|
14.6 KB |
sha256:18389e9aa943dd62adc91ad8aaa61a962c962f05e22e32fa455c3abab27da9ee
|
|
|
ringcentral-docker~node~VTZN6R.dockerbuild
|
14.1 KB |
sha256:4db30fb22b3dd2d8a5b4359b289c5faac510e039f025ab7c5f7c6ab2ec469852
|
|
|
ringcentral-docker~node~Y3TA8Y.dockerbuild
|
15.4 KB |
sha256:8cf10624992832bcd286dd9349cee6591de9acb6b2555d1a96cac6fb1eebc19d
|
|