-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
arm64 support #256
arm64 support #256
Conversation
@@ -4,7 +4,6 @@ | |||
"email": "[email protected]" | |||
}, | |||
"plugins": [ | |||
["docker", { "registry": "ejhayes/nodejs-bull-monitor", "tagLatest": false}], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wanted to have the build-push-action export to docker locally and keep the auto shipit action responsible for pushing to docker, but ran into this lmitation:
The default image store in Docker Engine doesn't support loading multi-platform images. You can enable the containerd image store, or push multi-platform images is to directly push to a registry, see registry.
https://docs.docker.com/engine/reference/commandline/buildx_build/#docker
|
||
- name: Prepare repository | ||
run: git fetch --unshallow --tags | ||
fetch-tags: true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this will give us what we need but it was hard for me to determine original reasoning here for the extra steps.
@@ -11,8 +11,6 @@ | |||
"scripts": { | |||
"prebuild": "rimraf dist", | |||
"build": "nest build", | |||
"ci:build": "npm run build && docker-compose build bull-monitor", | |||
"ci:publish": "npm run ci:build && docker-compose push bull-monitor", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't see ci:publish
getting used anywhere, and ci:build
functionality is encapsulated in the build-push-action step
➿ Code coverage
|
No description provided.