beenull/moby
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Fixed bad handling of "container not found" error

Browse source 
Create container job could fail because a container specified with
`--volumes-from` does not exist. This error is not propagated to client
though. Instead it's recognized by higher levels as "image not found".
Client then tries to pull the image and launch the container again.

This patch changes the lower level error message so that it's not
recognized as "image not found" and thus it's propagated to client.

Signed-off-by: Michal Minar <miminar@redhat.com>
This commit is contained in:
Michal Minar 2015-02-24 12:42:51 +01:00
parent 1d27930faa
commit d96e885314
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
daemon/volumes.go
View file

@ -279,7 +279,7 @@ func (container *Container) applyVolumesFrom() error {
c, err := container.daemon.Get(id)
if err != nil {
return err
return fmt.Errorf("Could not apply volumes of non-existent container %q.", id)
}
var (