Brian Goff b98eabeaed Validate mount paths on task create ...

This is intended as a minor fix for 1.12.1 so that task creation doesn't
do unexpected things when the user supplies erroneous paths.

In particular, because we're currently using hostConfig.Binds to setup
mounts, if a user uses an absolute path for a volume mount source, or a
non-absolute path for a bind mount source, the engine will do the
opposite of what the user requested since all absolute paths are
treated as binds and all non-absolute paths are treated as named
volumes.

Fixes #25253

Signed-off-by: Brian Goff <cpuguy83@gmail.com>
Upstream-commit: 38f8b0eb10725c40fb3c7e0719accd240cd39e22
Component: engine

2016-08-01 23:35:46 -04:00

..

adapter.go

add health check in docker cluster

2016-07-06 13:43:20 -07:00

container.go

Validate mount paths on task create

2016-08-01 23:35:46 -04:00

controller.go

container/controller: avoid cancellation with forked pull context

2016-07-25 21:52:10 -07:00

errors.go

add health check in docker cluster

2016-07-06 13:43:20 -07:00

executor.go

Using map to list plugins in node description

2016-07-25 17:45:32 -07:00

health_test.go

add health check in docker cluster

2016-07-06 13:43:20 -07:00

validate_test.go

Validate mount paths on task create

2016-08-01 23:35:46 -04:00

validate_unix_test.go

Validate mount paths on task create

2016-08-01 23:35:46 -04:00

validate_windows_test.go

Validate mount paths on task create

2016-08-01 23:35:46 -04:00

validate.go

Validate mount paths on task create

2016-08-01 23:35:46 -04:00