summaryrefslogtreecommitdiff
path: root/cmd/podman/utils
diff options
context:
space:
mode:
authorJordan Christiansen <xordspar0@gmail.com>2021-03-26 22:10:43 -0500
committerJordan Christiansen <xordspar0@gmail.com>2021-03-27 09:46:30 -0500
commitdce877c5ca190d06c9e9c069475bd17ea12e8ac9 (patch)
treea9647bb4fe42d8c4f765a8c5604469483088944a /cmd/podman/utils
parent4d0b583340c37efbf175c00d75d75107a0b23f00 (diff)
downloadpodman-dce877c5ca190d06c9e9c069475bd17ea12e8ac9.tar.gz
podman-dce877c5ca190d06c9e9c069475bd17ea12e8ac9.tar.bz2
podman-dce877c5ca190d06c9e9c069475bd17ea12e8ac9.zip
Add problematic volume name to kube play error messages
When kube play fails to create a volume, it should say which volume had the problem so the user doesn't have to guess. For the following pod spec: apiVersion: v1 kind: Pod metadata: name: mypod spec: containers: - name: myfrontend image: nginx volumeMounts: - mountPath: "/var/www/html" name: mypd volumes: - name: mypd hostPath: path: /var/blah podman will now report: Error: failed to create volume "mypd": error in parsing HostPath in YAML: error checking path "/var/blah": stat /var/blah: no such file or directory Signed-off-by: Jordan Christiansen <xordspar0@gmail.com>
Diffstat (limited to 'cmd/podman/utils')
0 files changed, 0 insertions, 0 deletions