I am trying to get DrivePool/CloudDrive working with Windows Containers. I've run into an issue that may be specific to DrivePool.
I am working on setting up a number of Windows Containers. These are native windows images running in Hyper-V using the Docker engine. I have several drives created in CD/DP. I have 1 Cloud Drive that is connected to a container with no problems. The other drive is 2 CloudDrives combined into a single DrivePool instance. This is the drive I am unable to mount to a container.
The error I receive is this:
Cannot start service radarr: CreateComputeSystem d88999382fbcd36ea97c92fdbcb5935dab2a1e6e52aaffecb3bc4779c46005d9: Do not attach the filter to the volume at this time.
I was able to mount the drive using SMB a Global Map on the host, but that seems to have problems of its own.
Is anyone else running a DrivePool instance attached to Windows Containers?
Question
ebalders
I am trying to get DrivePool/CloudDrive working with Windows Containers. I've run into an issue that may be specific to DrivePool.
I am working on setting up a number of Windows Containers. These are native windows images running in Hyper-V using the Docker engine. I have several drives created in CD/DP. I have 1 Cloud Drive that is connected to a container with no problems. The other drive is 2 CloudDrives combined into a single DrivePool instance. This is the drive I am unable to mount to a container.
The error I receive is this:
Cannot start service radarr: CreateComputeSystem d88999382fbcd36ea97c92fdbcb5935dab2a1e6e52aaffecb3bc4779c46005d9: Do not attach the filter to the volume at this time.
I was able to mount the drive using SMB a Global Map on the host, but that seems to have problems of its own.
Is anyone else running a DrivePool instance attached to Windows Containers?
Link to comment
Share on other sites
5 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.