Paweł Gronowski 0d51cf9db8 volume/local: Make host resolution backwards compatible ... Commit 8ae94cafa5 added a DNS resolution of the `device` part of the volume option. The previous way to resolve the passed hostname was to use `addr` option, which was handled by the same code path as the `nfs` mount type. The issue is that `addr` is also an SMB module option handled by kernel and passing a hostname as `addr` produces an invalid argument error. To fix that, restore the old behavior to handle `addr` the same way as before, and only perform the new DNS resolution of `device` if there is no `addr` passed. Signed-off-by: Paweł Gronowski <pawel.gronowski@docker.com>		2024-01-23 14:49:05 +01:00
..
drivers	migrate to github.com/containerd/log v0.1.0	2023-10-11 17:52:23 +02:00
local	volume/local: Make host resolution backwards compatible	2024-01-23 14:49:05 +01:00
mounts	volumes/subpath: Plumb context	2024-01-19 17:32:21 +01:00
service	migrate to github.com/containerd/log v0.1.0	2023-10-11 17:52:23 +02:00
testutils	linting: gosec: fix or suppress G112, G114 in test code	2022-09-04 15:36:51 +02:00
volume.go	Restore active mount counts on live-restore	2023-06-27 16:33:23 +00:00