Currently, we manage three custom Docker images for deploying the CDK stack: one housing various zkevm contracts (each fork tagged separately), another adapting the bridge UI to accommodate relative URLs, and a third for applying workloads.
The aim is to:
[x] 1. Streamline the organization of our Dockerfiles and forks.
[x] 2. Establish a daily or weekly cron job for building and pushing these images.
[ ] 3. Transition the hosting of these images from DockerHub to GCR.
=> For the moment, images are still hosted on the Docker Hub under my username. That's fine for now.
https://hub.docker.com/u/leovct
Other
Fix npm install random fails with ECONNRESET and ETIMEDOUT by upgrading npm to a version higher or equal to 10.5.1 (see the fix: https://github.com/npm/cli/pull/7324)
I enabled the CI to run on this PR. I'll remove it once we've tested that we can build and successfully send images to our GCR.
---
name: Docker Image Builder Cron
on:
schedule:
- cron: '0 6 * * 1' # Every Monday at 6 AM Paris time (UTC+2).
workflow_dispatch:
pull_request: # TODO: Remove this. This is just for testing purposes.
...
Description
Currently, we manage three custom Docker images for deploying the CDK stack: one housing various zkevm contracts (each fork tagged separately), another adapting the bridge UI to accommodate relative URLs, and a third for applying workloads.
The aim is to:
Other
npm install
random fails with ECONNRESET and ETIMEDOUT by upgradingnpm
to a version higher or equal to 10.5.1 (see the fix: https://github.com/npm/cli/pull/7324)hadolint
check in CI.Dockerfile
files.References (if applicable)
https://polygon.atlassian.net/browse/DVT-1467
Test
I enabled the CI to run on this PR. I'll remove it once we've tested that we can build and successfully send images to our GCR.
Jobs are progressing and images are being built.