Skip to content
This repository has been archived by the owner on Oct 13, 2023. It is now read-only.

[17.10] re-vndr libnetwork to 6c51292 and swarmkit to 872861d #264

Merged
merged 3 commits into from
Oct 11, 2017
Merged

Conversation

andrewhsu
Copy link
Contributor

@andrewhsu andrewhsu commented Oct 11, 2017

Re-vndr and cherry-pick a commit moby/moby@7e6b216 (cherry-pick went in clean) to update the DockerSwarmSuite.TestSwarmNetworkIPAMOptions test:

$ cd components/engine
$ vi vendor.conf
$ make BIND_DIR=. shell
$ vndr github.com/docker/libnetwork
$ vndr github.com/docker/swarmkit
$ exit
$ cd ../..
$ git cherry-pick -s -x -Xsubtree=components/engine 7e6b216

Brings in the following libnetwork changes:

Comparison of changes in libnetwork upstream: moby/libnetwork@0f08d31...6c51292

Brings in the following swarmkit changes:

Comparison of changes in swarmkit upstream: moby/swarmkit@941a018...872861d

Signed-off-by: Andrew Hsu <andrewhsu@docker.com>
@andrewhsu andrewhsu added this to the 17.10.0 milestone Oct 11, 2017
@fcrisciani
Copy link

fcrisciani commented Oct 11, 2017

I think there is a compilation error due to something in swarmkit missing...

00:28:37 [init] vendor/github.com/docker/swarmkit/manager/allocator/cnmallocator/portallocator.go:385: not enough arguments in call to ps.dynamicPortSpace.GetID
00:28:37 [init] 	have ()
00:28:37 [init] 	want (bool)
00:28:54 [init] Makefile-docker-ce:45: recipe for target 'binary-daemon' failed

@abhi is the bitseq change?

@vieux
Copy link
Contributor

vieux commented Oct 11, 2017

looks like moby/libnetwork@a2bcac0 is missing

Signed-off-by: Andrew Hsu <andrewhsu@docker.com>
@andrewhsu andrewhsu changed the title [17.10] re-vndr libnetwork to 6c51292 [17.10] re-vndr libnetwork to 6c51292 and swarmkit to 872861d Oct 11, 2017
Signed-off-by: Abhinandan Prativadi <abhi@docker.com>
(cherry picked from commit 7e6b216)
Signed-off-by: Andrew Hsu <andrewhsu@docker.com>
@andrewhsu
Copy link
Contributor Author

@vieux i think the original failure in compilation was because i did not also update the vendor to swarmkit. i've now updated the PR to vendor swarmkit up to the point similar to this PR to moby/moby moby/moby#35103

@andrewhsu
Copy link
Contributor Author

@johnstep @jhowardmsft this error has popped up on two of the build runs:

01:41:06.949 FAIL: docker_cli_restart_test.go:265: DockerSuite.TestRestartContainerwithRestartPolicy
01:41:06.949 
01:41:06.949 docker_cli_restart_test.go:282:
01:41:06.949     // Make sure we can stop/start (regression test from a705e166cf3bcca62543150c2b3f9bfeae45ecfa)
01:41:06.949     dockerCmd(c, "stop", id1)
01:41:06.949 c:/gopath/src/github.com/docker/docker/vendor/github.com/gotestyourself/gotestyourself/icmd/command.go:61:
01:41:06.950     t.Fatalf("at %s:%d - %s\n", filepath.Base(file), line, err.Error())
01:41:06.950 ... Error: at cli.go:33 - 
01:41:06.950 Command:  d:\CI\CI-a761ee3d4d\binary\docker.exe stop cdd38e2935426686a6a8abfee3e1ab3ac901f0212cf958a4d36889860837e86d
01:41:06.950 ExitCode: 1
01:41:06.950 Error:    exit status 1
01:41:06.950 Stdout:   
01:41:06.950 Stderr:   Error response from daemon: cannot stop container: cdd38e2935426686a6a8abfee3e1ab3ac901f0212cf958a4d36889860837e86d: Cannot kill container cdd38e2935426686a6a8abfee3e1ab3ac901f0212cf958a4d36889860837e86d: invalid container: cdd38e2935426686a6a8abfee3e1ab3ac901f0212cf958a4d36889860837e86d
01:41:06.950 
01:41:06.950 
01:41:06.950 Failures:
01:41:06.950 ExitCode was 1 expected 0
01:41:06.950 Expected no error

Copy link
Contributor

@abhi abhi left a comment

Choose a reason for hiding this comment

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

LGTM

@andrewhsu andrewhsu merged commit 9c61899 into docker-archive:17.10 Oct 11, 2017
@andrewhsu andrewhsu deleted the v branch October 11, 2017 17:46
docker-jenkins pushed a commit that referenced this pull request Feb 20, 2018
Update docker kill reference docs
Upstream-commit: bbe7f84540098a99c60b8f2c7514a7141da56d9b
Component: cli
docker-jenkins pushed a commit that referenced this pull request Jun 6, 2019
[19.03 backport] Windows: Don't attempt detach VHD for R/O layers
Upstream-commit: dde48c67151c8b009efa1baff806eb6d3bc1135b
Component: engine
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants