-
Notifications
You must be signed in to change notification settings - Fork 583
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
error extracting the metadata for a Quay.io image #5885
Comments
@actraiser2 Thank you for raising the issue. |
Here is the detailed stacktrace: 2024-08-05 12:05:37.336 DEBUG 1 --- [io-8080-exec-10] thorizationHeaderRequestRedirectStrategy : [!dt dt.entity.process_group=PROCESS_GROUP-A4C0D936FBECC05C, dt.trace_sampled=true, dt.trace_id=a18236f5615737891e2ba12d36df8aec, dt.entity.host_group=HOST_GROUP-7D678375C12400F3, dt.entity.process_group_instance=PROCESS_GROUP_INSTANCE-E027DA69DBB9DB9C, dt.host_group.id=HOST-USU, dt.span_id=b993d068e7e61a80, dt.entity.host=HOST-7B2BCC248E339F00] Redirect requested to location 'https://cdn03.quay.io/quayio-production-s3/sha256/3c/3c6a219e7df6ab6a8a7d27869b650409bfce69b51ff2b47ad2b4e4a336b53a43?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAI5LUAQGPZRPNKSJA%2F20240805%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20240805T100537Z&X-Amz-Expires=600&X-Amz-SignedHeaders=host&X-Amz-Signature=680adb9ff6bf7d002e1743a2c3cb4a47f5059cd4f109405d3744a34c3ddad0ec&cf_sign=RLQVmD3GBXY1k8Yh8I7J59IF6BLVJnoACVZ3D4bB72GpDz4Fsm9rhx7BL9nwWjaGwxfyhImhHXaFfYE8gwSbvixruJiaznEZBRL3oZWSIGdNriGfCVrtO53nKFniK%2BFflmzjv9auijMZhEqMjxrbSEITr9hVR2XHwIImo0inq8blhCCUsK%2FnJkmxMfIqrwQQ5nKTbSzKWcQAKlbk7tnqQmMkM%2FrPwbn2BMjr%2FqsD8xw4nWkgFUErT9zdtIhNfd3ANIRQBG8H1n7VrToLIuKMAUcxJncaeny67xDU0oG8QcpdIue6L437UEgwTjh5L%2FjjEj7DfKWhr3KQC5l2Xz0eYg%3D%3D&cf_expiry=1722852937®ion=us-east-1&namespace=actraiser&username=actraiser%2Bcicd_pull&repo_name=sl-financiero-financiero-batch-apertura-tramites-sf-recibos' org.springframework.web.client.UnknownContentTypeException: Could not extract response: no suitable HttpMessageConverter found for response type [interface java.util.Map] and content type [binary/octet-stream] |
Quay.io responds with binary/octet-stream when reading imageBlob. application/octet-stream is identical to binary/octet-stream. Fixes spring-cloud#5885
@actraiser2 Would you mind checking out PR #5892 and letting us know if the problem is resolved when using quay.io? git checkout https://github.com/spring-cloud/spring-cloud-dataflow.git
cd spring-cloud-dataflow
gh pr checkout 5892
./mvnw clean package -am -pl spring-cloud-dataflow-server -DskipTests
# if using k8s test
./mvnw spring-boot:build-image -pl spring-cloud-dataflow-server |
@actraiser2 Have you had a chance to kick the tires on this PR? |
Closing this issue due to inactivity. If this issue needs to be reopened, please leave a comment. Thank you! |
Description:
I'm obtaining the following error when trying to get the application metadata related to quay.io image:
org.springframework.web.client.UnknownContentTypeException: Could not extract response: no suitable HttpMessageConverter found for response type [interface java.util.Map] and content type [binary/octet-stream]
Release versions:
Latest version: 2.11.4
Steps to reproduce:
This is the configuration associated to the quay.io registry in the application.yaml:
.....
dataflow
container:
registry-configurations:
quay:
registry-host: quay.io
authorization-type: dockeroauth2
user: ${QUAY_USERNAME}
secret: ${QUAY_PASSWORD}
extra:
registryAuthUri: "https://quay.io/v2/auth?service=quay.io&scope=repository:{repository}:pull"_
Screenshots:
*Additional context:
The error produces after spring cloud data flow has redirected to the following ur.l:
https://cdn03.quay.io/quayio-production-s3/sha256/dd/dd1561170543fb2b2fa23c0ff7b880ebd34db620d4a38faf2822cef0ce6cc12c?X-Amz-Algorithm=AWS4-HMAC-SHA256&....................................
If i curl the previous url, i can get all the image metadata with a response header Content-Type: binary/octet-stream, that Spring doesn't like:
**{
"architecture": "amd64",
"created": "2024-06-11T07:53:55.512358385Z",
"history": [
..........
}
"config": {
"Entrypoint": [
.....
"Env": [
"......
],
"Labels": {
......
},
}
}**
The text was updated successfully, but these errors were encountered: