-
Notifications
You must be signed in to change notification settings - Fork 517
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
Version 4.2.0 messed up with the json from the metadata action #956
Comments
It seems linked to #872 where your docker config in You altered the content of the config in
You append Also About the error message, I will make some changes to make it clear it's an issue parsing the configuration and also warn if there is an issue instead. |
Thank you it's very interesting to read, we will fix it at our side and remove |
With #872 we now display the proxy configuration which is read from |
Thank you :) |
Contributing guidelines
I've found a bug, and:
Description
After the version 4.2.0 came out our pipeliens fail if we use docker/build-push-action@v4 so we had to pin it to version 4.1.1.
There is some issue with interprate the jsons given by the docker/metadata-action@v4
Expected behaviour
The action works with the medata generated by docker/metadata-action@v4
Actual behaviour
If we use it with the we get
Run docker/build-push-action@v4 GitHub Actions runtime token ACs Docker info Error: Unexpected token { in JSON at position 253
Repository URL
https://github.com/hpi-schul-cloud/schulcloud-server
Workflow run URL
https://github.com/hpi-schul-cloud/schulcloud-server/actions/runs/6120036347/job/16611111071
YAML workflow
Workflow logs
log.txt
BuildKit logs
No response
Additional info
No response
The text was updated successfully, but these errors were encountered: