-
Notifications
You must be signed in to change notification settings - Fork 2
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
Fix Docker build IV #13
Conversation
15f6abf
to
ebcc5b7
Compare
.github/workflows/docker.yml
Outdated
|
||
jobs: | ||
build-env-image: | ||
runs-on: ubuntu-24.04 | ||
env: | ||
REGISTRY_IMAGE: ghcr.io/andy5995/vs-fltk |
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.
This worked on my fork https://github.com/andy5995/vs-fltk/pkgs/container/vs-fltk
I do vaguely recalling getting a PAT to use ghcr from the command line. These instructions seem to confusingly indicate that a PAT isn't needed to push from a workflow though. |
@KaruroChori could you please check the repo settings mentioned here? docker/build-push-action#687 (comment) |
Thank you for you help! |
|
||
on: | ||
pull_request: | ||
branches: master | ||
paths: | ||
- '**Dockerfile' | ||
- '**docker.yml' | ||
- 'docker/**' |
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 figured we want the docker tests to run if any file except for the README is changed, because the tests works in conjunction with the scripts and docker-compose.yml... Hmmm... but maybe different filters are needed for docker.yml.
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.
but maybe different filters are needed for docker.yml.
I reverted the change below in docker.yml. In theory, if it passes this test, there's no reason to trigger it for the other one. The build should have already been triggered by any changes here.. or not...
I dunno. Let me know what you think. Or we could avoid some thought and adjust later as needed.
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 opened an issue so that I don't forget about this and we can delay the decision as right now I don't have strong feelings about one or the other option :D.
I'm glad you got it working. It looks like only the buildcache was pushed though. That's because I forgot the 'tags' key (which is included in this PR). |
c0b79aa
to
d403e18
Compare
This reverts commit 2ce41d2.
d403e18
to
11ffe8a
Compare
Rebased. Up to date with master @ 330bf4e |
@andy5995 I left some notes in the review, I will have to address those before merging it. |
Portable owner name & repo names back again
(Fixes #7)