summaryrefslogtreecommitdiff
path: root/cmd/podman/shared/volumes_shared.go
diff options
context:
space:
mode:
authorMatthew Heon <matthew.heon@pm.me>2019-10-23 16:34:32 -0400
committerMatthew Heon <matthew.heon@pm.me>2019-10-23 16:34:32 -0400
commit84eea2b2c09385078d7b147954ec9be3da608214 (patch)
tree58fae8694c4c9f167ae9d8ce1ef2c6c52f161c5e /cmd/podman/shared/volumes_shared.go
parent2e6c9aa4901b30653d814f4984663cf07fc5e57f (diff)
downloadpodman-84eea2b2c09385078d7b147954ec9be3da608214.tar.gz
podman-84eea2b2c09385078d7b147954ec9be3da608214.tar.bz2
podman-84eea2b2c09385078d7b147954ec9be3da608214.zip
Return a better error for volume name conflicts
When you try and create a new volume with the name of a volume that already exists, you presently get a thoroughly unhelpful error from `mkdir` as the volume attempts to create the directory it will be mounted at. An EEXIST out of mkdir is not particularly helpful to Podman users - it doesn't explain that the name is already taken by another volume. The solution here is potentially racy as the runtime is not locked, so someone else could take the name while we're still getting things set up, but that's a narrow timing window, and we will still return an error - just an error that's not as good as this one. Signed-off-by: Matthew Heon <matthew.heon@pm.me>
Diffstat (limited to 'cmd/podman/shared/volumes_shared.go')
0 files changed, 0 insertions, 0 deletions