Thanks to visit codestin.com
Credit goes to github.com

Skip to content

fixes github actions #1447

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 4 commits into from
Jun 18, 2022
Merged

fixes github actions #1447

merged 4 commits into from
Jun 18, 2022

Conversation

rhtenhove
Copy link
Contributor

@rhtenhove rhtenhove commented Jun 18, 2022 •
edited
Loading

This fixes the problem introduced by #1442 . Also updated the workflow versions.

I've also made the :stable tag explicit everywhere. That should make it more clear for every user what they're pulling. Also follows the recommendation that you should always use a tagged image. :latest still points to stable, so nothing changes for existing users.

So to keep with that idea, I've also added a push for tagged releases, so things like aflplusplus/aflplusplus:4.00d will work in the future.

Finally, as now everyone is hosting a registry, and some container daemons decided to not enforce docker.io as the default anymore, I've made them all fully qualified, i.e.: docker.io/aflplusplus/aflplusplus:stable.

WDYT ?

@vanhauser-thc
Copy link
Member

lets try if it works :)

@vanhauser-thc vanhauser-thc merged commit 5d5d1f7 into AFLplusplus:dev Jun 18, 2022
@rhtenhove
Copy link
Contributor Author

It works! :)

Currently fuzzing with :dev

@vanhauser-thc
Copy link
Member

hmm there is still something wrong, the dev one is not being built anymore:

/usr/bin/docker pull tonistiigi/binfmt:latest
Error response from daemon: Head "https://registry-1.docker.io/v2/tonistiigi/binfmt/manifests/latest": Get "https://auth.docker.io/token?account=githubactions&scope=repository%3Atonistiigi%2Fbinfmt%3Apull&service=registry.docker.io": EOF

maybe the tonistiigi docker registry is not a good one to use?

@rhtenhove
Copy link
Contributor Author

hmm there is still something wrong, the dev one is not being built anymore:

/usr/bin/docker pull tonistiigi/binfmt:latest Error response from daemon: Head "https://registry-1.docker.io/v2/tonistiigi/binfmt/manifests/latest": Get "https://auth.docker.io/token?account=githubactions&scope=repository%3Atonistiigi%2Fbinfmt%3Apull&service=registry.docker.io": EOF

maybe the tonistiigi docker registry is not a good one to use?

I also see this in the Docker login action of the latest (cpubind) merge:

Error: Error response from daemon: Get "https://registry-1.docker.io/v2/": received unexpected HTTP status: 503 Service Unavailable

It seems Dockerhub had some downtime. Can you rerun the workflow?

The tonistiigi is the default image used by the QEMU action to emulate arm64. Best not to change that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@rhtenhove @vanhauser-thc