This repository was archived by the owner on Apr 14, 2026. It is now read-only.
Tags: kserve/modelmesh-minio-examples
Tags
fix: Update base minio image (#11) Use the base image docker.io/minio/minio:RELEASE.2021-06-17T00-10-46Z.hotfix.35a0912ff --------- Signed-off-by: Rafael Vasquez <rafvasq21@gmail.com> Signed-off-by: Christian Kadner <ckadner@us.ibm.com> Co-authored-by: Christian Kadner <ckadner@us.ibm.com>
fix: Update base minio image (#11) Use the base image docker.io/minio/minio:RELEASE.2021-06-17T00-10-46Z.hotfix.35a0912ff --------- Signed-off-by: Rafael Vasquez <rafvasq21@gmail.com> Signed-off-by: Christian Kadner <ckadner@us.ibm.com> Co-authored-by: Christian Kadner <ckadner@us.ibm.com>
Fix group ownership and file permissions OpenShift runs containers using an arbitrarily assigned user ID, the group ID must always be set to the root group (0) so the /data1 folder and model files that the minio server process needs to access must have their group ownership set to the root group. They also need to be read/writable by that group as per OpenShift Container Platform-specific guidelines. https://developers.redhat.com/blog/2020/10/26/adapting-docker-and-kubernetes-containers-to-run-on-red-hat-openshift-container-platform#group_ownership_and_file_permission Resolves kserve/modelmesh-serving#215 Signed-off-by: Christian Kadner <ckadner@us.ibm.com>
Fix group ownership and file permissions OpenShift runs containers using an arbitrarily assigned user ID, the group ID must always be set to the root group (0) so the /data1 folder and model files that the minio server process needs to access must have their group ownership set to the root group. They also need to be read/writable by that group as per OpenShift Container Platform-specific guidelines. https://developers.redhat.com/blog/2020/10/26/adapting-docker-and-kubernetes-containers-to-run-on-red-hat-openshift-container-platform#group_ownership_and_file_permission Resolves kserve/modelmesh-serving#215 Signed-off-by: Christian Kadner <ckadner@us.ibm.com>
Fix group ownership and file permissions OpenShift runs containers using an arbitrarily assigned user ID, the group ID must always be set to the root group (0) so the /data1 folder and model files that the minio server process needs to access must have their group ownership set to the root group. They also need to be read/writable by that group as per OpenShift Container Platform-specific guidelines. https://developers.redhat.com/blog/2020/10/26/adapting-docker-and-kubernetes-containers-to-run-on-red-hat-openshift-container-platform#group_ownership_and_file_permission Resolves kserve/modelmesh-serving#215 Signed-off-by: Christian Kadner <ckadner@us.ibm.com>
Fix group ownership and file permissions OpenShift runs containers using an arbitrarily assigned user ID, the group ID must always be set to the root group (0) so the /data1 folder and model files that the minio server process needs to access must have their group ownership set to the root group. They also need to be read/writable by that group as per OpenShift Container Platform-specific guidelines. https://developers.redhat.com/blog/2020/10/26/adapting-docker-and-kubernetes-containers-to-run-on-red-hat-openshift-container-platform#group_ownership_and_file_permission Resolves kserve/modelmesh-serving#215 Signed-off-by: Christian Kadner <ckadner@us.ibm.com>
Fix group ownership and file permissions OpenShift runs containers using an arbitrarily assigned user ID, the group ID must always be set to the root group (0) so the /data1 folder and model files that the minio server process needs to access must have their group ownership set to the root group. They also need to be read/writable by that group as per OpenShift Container Platform-specific guidelines. https://developers.redhat.com/blog/2020/10/26/adapting-docker-and-kubernetes-containers-to-run-on-red-hat-openshift-container-platform#group_ownership_and_file_permission Resolves kserve/modelmesh-serving#215 Signed-off-by: Christian Kadner <ckadner@us.ibm.com>
Fix group ownership and file permissions OpenShift runs containers using an arbitrarily assigned user ID, the group ID must always be set to the root group (0) so the /data1 folder and model files that the minio server process needs to access must have their group ownership set to the root group. They also need to be read/writable by that group as per OpenShift Container Platform-specific guidelines. https://developers.redhat.com/blog/2020/10/26/adapting-docker-and-kubernetes-containers-to-run-on-red-hat-openshift-container-platform#group_ownership_and_file_permission Resolves kserve/modelmesh-serving#215 Signed-off-by: Christian Kadner <ckadner@us.ibm.com>