Michal Minar bddb299991 Fixed bad handling of "container not found" error ...

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>
Upstream-commit: d96e8853145ed6a03529e093c49b91f0053472a6
Component: engine

2015-02-24 15:52:47 +01:00

components/engine

Fixed bad handling of "container not found" error

2015-02-24 15:52:47 +01:00

Description

No description provided

310 MiB

Languages

Go 92%

Shell 5.5%

Dockerfile 1.1%

Go-Checksums 0.9%

Makefile 0.3%

Other 0.2%