mirror of
https://github.com/moby/moby.git
synced 2022-11-09 12:21:53 -05:00
8663d09334
It has been pointed out that sometimes device mapper unit tests fail with the following diagnostics: > --- FAIL: TestDevmapperSetup (0.02s) > graphtest_unix.go:44: graphdriver: loopback attach failed > graphtest_unix.go:48: loopback attach failed The root cause is the absence of udev inside the container used for testing, which causes device nodes (/dev/loop*) to not be created. The test suite itself already has a workaround, but it only creates 8 devices (loop0 till loop7). It might very well be the case that the first few devices are already used by the system (on my laptop 15 devices are busy). The fix is to raise the number of devices being manually created. Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com> |
||
|---|---|---|
| .. | ||
| aufs | ||
| btrfs | ||
| copy | ||
| devmapper | ||
| graphtest | ||
| lcow | ||
| overlay | ||
| overlay2 | ||
| overlayutils | ||
| quota | ||
| register | ||
| vfs | ||
| windows | ||
| zfs | ||
| counter.go | ||
| driver.go | ||
| driver_freebsd.go | ||
| driver_linux.go | ||
| driver_test.go | ||
| driver_unsupported.go | ||
| driver_windows.go | ||
| errors.go | ||
| fsdiff.go | ||
| plugin.go | ||
| proxy.go | ||