OpenShift技术问询：Minishift部署的Java应用如何访问Windows C盘文件？

Hey there, let's tackle this problem head-on. Since your Java app is up and running in Minishift but needs to read/write to a specific folder on your Windows C drive (that can't be moved into the container), here are three reliable solutions you can implement:

1. Use Host Path Volumes (Simplest Local Approach) #

Host Path volumes let you mount a directory from your Windows host directly into your container. Here's how to set this up:

• First, confirm how Minishift maps your Windows C drive. Depending on your hypervisor (Hyper-V, VirtualBox), the path might look like /mnt/c/your-specified-folder (Hyper-V) or /c/your-specified-folder (some VirtualBox setups).
• Edit your app's DeploymentConfig (or Deployment) to add the volume and mount it:

  spec:
    template:
      spec:
        volumes:
        - name: windows-c-drive-volume
          hostPath:
            path: /mnt/c/your-specified-folder  # Replace with your mapped path
            type: Directory
        containers:
        - name: your-java-app-container
          volumeMounts:
          - name: windows-c-drive-volume
            mountPath: /app/windows-files  # Path inside the container your app will access
  

• Run oc edit dc <your-app-deployment-config-name> to apply this change, or use oc apply -f <updated-deployment-file.yaml>.
• Critical note: Make sure the Windows folder has read/write permissions enabled for the user that Minishift's virtual machine runs as (you can temporarily grant permissions to "Everyone" for testing). Your Java app should now interact with /app/windows-files (inside the container) which maps directly to your C drive folder.

2. SMB/CIFS Volume (For More Controlled Access) #

If host path mapping gives you permission headaches, you can share the Windows folder via SMB and mount it as a CIFS volume in Minishift:

1. Share the C drive folder on Windows: Right-click the folder > Properties > Sharing > Advanced Sharing > Check "Share this folder". Set permissions so the Minishift VM can access it.
2. Create a Secret to store SMB credentials:

   oc create secret generic smb-secret --from-literal=username=<your-windows-username> --from-literal=password=<your-windows-password>
   

3. Create a PersistentVolume (PV):

   apiVersion: v1
   kind: PersistentVolume
   metadata:
     name: smb-pv
   spec:
     capacity:
       storage: 1Gi  # Adjust based on your needs
     accessModes:
       - ReadWriteMany
     persistentVolumeReclaimPolicy: Retain
     csi:
       driver: smb.csi.k8s.io
       volumeHandle: smb-volume-1
       volumeAttributes:
         source: "//<your-windows-ip>/<shared-folder-name>"
       nodeStageSecretRef:
         name: smb-secret
   

4. Create a PersistentVolumeClaim (PVC) to bind the PV:

   apiVersion: v1
   kind: PersistentVolumeClaim
   metadata:
     name: smb-pvc
   spec:
     accessModes:
       - ReadWriteMany
     resources:
       requests:
         storage: 1Gi
   

5. Mount the PVC to your app container: Update your DeploymentConfig to include the volume mount, similar to the host path method but using the PVC name instead.

3. Verify Container Permissions #

Whichever method you choose, double-check that the user running your Java app inside the container has read/write access to the mounted directory. You can exec into the container to test:

oc rsh <your-app-pod-name>
# Then try creating a file in the mounted path
touch /app/windows-files/test-file.txt

If you get a permission error, you might need to adjust the security context in your DeploymentConfig to run the container as a user with appropriate permissions, or tweak the Windows folder's security settings.

内容的提问来源于stack exchange，提问作者Sasha Korkin