Skip to content

Run buildkit integration tests#40023

Closed
tiborvass wants to merge 3 commits intomoby:masterfrom
tiborvass:buildkit_tests
Closed

Run buildkit integration tests#40023
tiborvass wants to merge 3 commits intomoby:masterfrom
tiborvass:buildkit_tests

Conversation

@tiborvass
Copy link
Copy Markdown
Contributor

Signed-off-by: Sam Whited sam@samwhited.com

@SamWhited SamWhited force-pushed the buildkit_tests branch 2 times, most recently from 3c5f8cc to e54c2ff Compare September 30, 2019 22:15
@SamWhited SamWhited force-pushed the buildkit_tests branch 12 times, most recently from 2049cf3 to 78cbc04 Compare October 3, 2019 16:28
@SamWhited SamWhited force-pushed the buildkit_tests branch 13 times, most recently from eb5108d to 3435fa3 Compare October 8, 2019 14:51
@SamWhited SamWhited force-pushed the buildkit_tests branch 9 times, most recently from f3cda46 to 20c5213 Compare October 24, 2019 16:59
Makefile Outdated
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

binary alone should be enough

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed

Makefile Outdated
Copy link
Copy Markdown
Contributor Author

@tiborvass tiborvass Oct 31, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You are testing the docker daemon that's provided by Jenkins, not the docker daemon in the codebase (ok you bind mount the binary but that's not enough). If you look at how test-docker-py works as an example, that runs inside the container: $(DOCKER_RUN_DOCKER) hack/make.sh dynbinary test-docker-py and buildkit should do the same. So you do need a hack/make/test-buildkit in moby that will call into buildkit's /hack/test integration from within the container.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The reason this ended up being changed was because the buildkit integration tests also try to launch containers and the docker-in-docker stuff was likely to be a source of problems and confusion, although I don't remember the specific issues I was running into. I'll go reread the conversation with @thaJeztah and play around with reverting it back; thanks!

@andrewhsu
Copy link
Copy Markdown
Contributor

@SamWhited i added b43076e to always generate a bundle tgz for the buildkit step. see b43076e#diff-58231b16fdee45a03a4ee3cf94a9f2c3R113 for how it collects files to put into the tgz.

@SamWhited
Copy link
Copy Markdown
Contributor

SamWhited commented Nov 5, 2019

💚 tests! Going to work on getting a more recent commit of Docker vendored in buildkit, and then update the buildkit commit used in these tests and re-enable all the other tests now.

@SamWhited
Copy link
Copy Markdown
Contributor

SamWhited commented Nov 7, 2019

Roadmap:

@SamWhited
Copy link
Copy Markdown
Contributor

@tibor can you mark this as ready for review? I don't have permissions. Thanks!

@thaJeztah
Copy link
Copy Markdown
Member

moved it out of draft

@AkihiroSuda
Copy link
Copy Markdown
Member

What's current status?

@SamWhited
Copy link
Copy Markdown
Contributor

Just needs review and merge, IIRC, all requested changes should have been made or explained.

Copy link
Copy Markdown
Member

@AkihiroSuda AkihiroSuda left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM if green

@thaJeztah
Copy link
Copy Markdown
Member

@SamWhited could you rebase the PR to force CI to run again?

Dockerfile Outdated
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this looks to be v2.7.0-rc.0 distribution/distribution@17b3ff1

Could you use v2.7.1 here (pin by commit: 2461543d988979529609e8cb6fca9ca190dc48da, but add a comment what version it is)

(Also curious; was this needed to make the tests pass?)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed. I don't remember why this was needed now, sadly.

@SamWhited
Copy link
Copy Markdown
Contributor

As soon as #40814 is merged this can be rebased, pointed at vendor, and then it will also be ready for merge. /cc @tonistiigi

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

buildkitd should not be needed

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oops. Fixed.

SamWhited and others added 3 commits April 15, 2020 16:54
Signed-off-by: Sam Whited <sam@samwhited.com>
Signed-off-by: Andrew Hsu <andrewhsu@docker.com>
Signed-off-by: Sam Whited <sam@samwhited.com>
Signed-off-by: Sam Whited <sam@samwhited.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants