Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Conversation

vieux
Copy link
Contributor

@vieux vieux commented Feb 22, 2017

image/cache: fix isValidParent logic #31189
Prevent freeing a possible invalid pointer from journald #31231
Synchronize the cursor returned by followJournal #31263
Fix duplicate mount points for multiple --volumes-from in docker run #29563
Shutdown leaks an error when the container was never started #31279

@vieux vieux added this to the 17.03.0 milestone Feb 22, 2017
@vieux vieux self-assigned this Feb 22, 2017
@thaJeztah
Copy link
Member

@vieux CI is failing

22:14:11 # github.com/docker/docker/integration-cli
22:14:11 ./docker_cli_build_test.go:7091: too many arguments in call to fakeContext
22:14:11 ./docker_cli_build_test.go:7091: multiple-value fakeContext() in single-value context
22:14:11 ./docker_cli_build_test.go:7094: undefined: buildImageSuccessfully
22:14:11 ./docker_cli_build_test.go:7094: undefined: withExternalBuildContext
22:14:11 ./docker_cli_build_test.go:7095: too many arguments in call to getIDByName
22:14:11 ./docker_cli_build_test.go:7095: multiple-value getIDByName() in single-value context
22:14:11 ./docker_cli_build_test.go:7098: undefined: withBuildFlags
22:14:11 ./docker_cli_build_test.go:7098: undefined: withExternalBuildContext
22:14:11 ./docker_cli_build_test.go:7098: multiple-value buildImage() in single-value context
22:14:11 ./docker_cli_build_test.go:7100: too many arguments in call to getIDByName
22:14:11 ./docker_cli_build_test.go:7100: too many errors

@thaJeztah thaJeztah added the status/failing-ci Indicates that the PR in its current state fails the test suite label Feb 22, 2017
Signed-off-by: Antonio Murdaca <runcom@redhat.com>
(cherry picked from commit 1cf4b2b)
Signed-off-by: Victor Vieux <victorvieux@gmail.com>
Signed-off-by: Kenfe-Mickael Laventure <mickael.laventure@gmail.com>
(cherry picked from commit 81630df)
Signed-off-by: Victor Vieux <victorvieux@gmail.com>
@vieux vieux removed the status/failing-ci Indicates that the PR in its current state fails the test suite label Feb 22, 2017
Make sure that the cursor value returned by followJournal() is the last
of the values returned by its goroutine's calls to drainJournal() by
waiting for it, rather than returning a value that may be superceded by
another if we're singalling the goroutine that it should exit by closing
a pipe.

Signed-off-by: Nalin Dahyabhai <nalin@redhat.com>
(cherry picked from commit d57c330)
Signed-off-by: Victor Vieux <victorvieux@gmail.com>
@vieux vieux changed the title [WIP] 17.03 cherry-picks 17.03 cherry-picks Feb 23, 2017
@vieux vieux force-pushed the 17.03-cherry branch 3 times, most recently from d66abc6 to 7d9967a Compare February 23, 2017 07:15
This fix tries to fix the issue raised in 21845. The issue with 21845
is that if multiple `--volumes-from` with the same destination has been
specified, then one volume will be overridden by the other. This will mess
up with volumes reference and prevent the overridden volume from
being removed at the end.

Issue 21845 was observed with `docker-compose` though it is possible to
emulate the same behavior with `docker` alone:
```
$ cat Dockerfile
FROM busybox
VOLUME ["/tmp/data"]
$ docker build -t vimage .
$ docker run --name=data1 vimage true
$ docker run --name=data2 vimage true
$ docker run --name=app --volumes-from=data1 --volumes-from=data2 -d busybox top
$ docker rm -f -v $(docker ps -aq)
$ docker volume ls
$ docker volume rm ...
```
NOTE: Second case:
```
$ cat Dockerfile
FROM busybox
VOLUME ["/tmp/data"]
$ docker build -t vimage .
$ docker run --name=data1 vimage true
$ docker run --name=data2 vimage true
$ docker run --name=app --volumes-from=data1 --volumes-from=data2 -v /tmp/data:/tmp/data -d busybox top
$ docker rm -f -v $(docker ps -aq)
$ docker volume ls
$ docker volume rm ...
```
NOTE: Third case: Combination of --volumes-from and `HostConfig.Mounts` (API only)

This fix tries to address the issue by return an error if duplicate
mount points was used with `--volumes-from`.

An integration test has been added.

This fix fixes 21845.

Signed-off-by: Yong Tang <yong.tang.github@outlook.com>
(cherry picked from commit 9526e5c)
Signed-off-by: Victor Vieux <victorvieux@gmail.com>
CHANGELOG.md Outdated
Copy link
Member

Choose a reason for hiding this comment

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

on close

vieux and others added 2 commits February 22, 2017 23:59
Signed-off-by: Victor Vieux <victorvieux@gmail.com>
I found that sometimes tasks would end up in a rejected state when
trying to update them quickly. The problem was that Shutdown could fail
if called before the container was started. Instead of returning an
error in this case, Shutdown should succeed. This allows tasks to
progress to the "shutdown" state as expected.

Signed-off-by: Aaron Lehmann <aaron.lehmann@docker.com>
(cherry picked from commit 37b492a)
Signed-off-by: Victor Vieux <victorvieux@gmail.com>
Copy link
Member

@thaJeztah thaJeztah left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Member

@vdemeester vdemeester left a comment

Choose a reason for hiding this comment

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

LGTM 🦁

@vieux vieux merged commit faa90e9 into moby:17.03.x Feb 23, 2017
@vieux vieux deleted the 17.03-cherry branch February 23, 2017 10:02
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.

8 participants

Morty Proxy This is a proxified and sanitized view of the page, visit original site.