-
Notifications
You must be signed in to change notification settings - Fork 18.7k
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
vendor: github.com/moby/buildkit v0.13.0-rc2 #47364
Conversation
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
@stewartsmith @PeterCai7 are you able to help with the cloudwatch logger? @vvoland perhaps we can move that update to a separate PR in preparation? |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
Thanks for looking at it @vvoland, I will review your comments shortly |
ec937c9
to
18b2ec4
Compare
18b2ec4
to
de9995f
Compare
Extracted the AWS bump to: #47373 |
de9995f
to
c02ca9f
Compare
Looks like increasing the integration tests timeout from 5m to 10m solves the Comparing (this PR): looks like indeed the tests take more time to complete, for example: these don't use build related things (and integration tests will use the legacy builder anyway), so wondering if it's the OTEL stuff that's making things slower? EDIT: Solved with d32b3cf (OTEL was trying to export spans over a wrong protocol and was slowing down all scopes that were being traced). |
0fcd7b9
to
5dc8d1d
Compare
This also fails consistently:
|
0bda842
to
1638943
Compare
e4a6f85
to
e6dfbdc
Compare
Rebased after #47245 merge |
e6dfbdc
to
b84098f
Compare
Updated to rc2 |
b84098f
to
33143e3
Compare
if err != nil { | ||
return struct{}{}, err | ||
} | ||
|
||
p.ref = newRef |
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.
Is this correct?
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.
Oh, good catch!
Yeah it looks like this shouldn't be deleted.
I restored it as:
p.ref = ref.String()
because ResolveImageConfig
no longer returns a reference.
Looking at the old implementation, it didn't really change the ref that was passed as an argument.
The only place where it returned a different ref is where it went to the (remotes.Resolver) Resolve()
, but it doesn't seem to change it either (at least the docker
remote).
Signed-off-by: CrazyMax <1951866+crazy-max@users.noreply.github.com> Signed-off-by: Paweł Gronowski <pawel.gronowski@docker.com>
Signed-off-by: Paweł Gronowski <pawel.gronowski@docker.com>
Introduced in: moby/buildkit@3713178 Signed-off-by: Paweł Gronowski <pawel.gronowski@docker.com>
StaticDirSource definition changed and can no longer be initialized from the composite literal. https://github.com/moby/buildkit/commits/a80b48544c029f0e28e1243407b55c916c7757f2 Signed-off-by: Paweł Gronowski <pawel.gronowski@docker.com>
moby/buildkit@1c1777b added an explicit id argument to the Resolve method. Signed-off-by: Paweł Gronowski <pawel.gronowski@docker.com>
moby/buildkit@e358792 changed that field to a function and added an `OverrideResource` function that allows to override it. Signed-off-by: Paweł Gronowski <pawel.gronowski@docker.com>
moby/buildkit@8bfd280 added a new argument that allows to specify different runtime. Signed-off-by: Paweł Gronowski <pawel.gronowski@docker.com>
Adjust to cache sources changes from: moby/buildkit@6b27487 Signed-off-by: Paweł Gronowski <pawel.gronowski@docker.com>
Signed-off-by: Paweł Gronowski <pawel.gronowski@docker.com>
Signed-off-by: Paweł Gronowski <pawel.gronowski@docker.com>
moby/buildkit@30c069c removed the `ResolveImageConfig` method in favor of more generic `ResolveSourceMetadata` that can also support other things than images. Signed-off-by: Paweł Gronowski <pawel.gronowski@docker.com>
Temporarily store the produced config descriptor for the buildkit history to work. Signed-off-by: Paweł Gronowski <pawel.gronowski@docker.com>
Signed-off-by: CrazyMax <1951866+crazy-max@users.noreply.github.com> Signed-off-by: Paweł Gronowski <pawel.gronowski@docker.com>
Buildkit added support for exporting metrics in: moby/buildkit@7de2e4f Explicitly set the protocol for exporting metrics like we do for the traces. We need that because Buildkit defaults to grpc. Signed-off-by: Paweł Gronowski <pawel.gronowski@docker.com>
33143e3
to
2d31532
Compare
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.
LGTM
discussed on Slack; looks like the failures are flaky tests, so no need to re-run CI again for now.
- What I did
Updated buildkit to v0.13.0-rc2
- How I did it
See individual commits.
- How to verify it
- Description for the changelog
- A picture of a cute animal (not mandatory but encouraged)