You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"The volumeMount is clashing with an already existing volumeMount with the same mountPath but a different content. \
31
-
The clashing mountPath is {clashing_mount_path:?}, \
32
-
the existing mount's volume name is {existing_volume_name:?} \
33
-
and the new mount's volume name is {new_volume_name:?}. \
34
-
Please have a look at the log/traces for details"
31
+
"Colliding mountPath {mount_path:?} in volumeMounts with different content. \
32
+
Existing volume name {existing_volume_name:?}, new volume name {new_volume_name:?}"
35
33
))]
36
-
ClashingMountPath{
37
-
clashing_mount_path:String,
34
+
MountPathCollision{
35
+
mount_path:String,
38
36
existing_volume_name:String,
39
37
new_volume_name:String,
40
38
},
@@ -219,25 +217,24 @@ impl ContainerBuilder {
219
217
/// Historically this function unconditionally added volumeMounts, which resulted in invalid
220
218
/// [`k8s_openapi::api::core::v1::PodSpec`]s, as volumeMounts where added multiple times - think of Trino using the same [`crate::commons::s3::S3Connection`]
221
219
/// two times, resulting in e.g. the s3 credentials being mounted twice as the same volumeMount.
0 commit comments