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
I have a question regarding how to configure additional data volumes in OpenCloud. I would appreciate it if you could provide some guidance.
My current setup is as follows:
I have installed OpenCloud in a Docker container on a Proxmox host. The application is running very well. I recently added a new disk to my system and successfully configured it as an LVM-Thin volume. The disk is visible and accessible from within the OpenCloud container at the path /var/lib/opencloud-sda/sda.
I have attempted to configure this new disk as an additional volume using the following methods, but they have not worked:
My current docker-compose.yml and .env files are configured to use a primary data volume defined by the OC_DATA_DIR environment variable.
First attempt:
I added a new bind mount directly to docker-compose.yml to make the new volume available to the container.
With this setup, the new volume was not recognized by OpenCloud.
Second attempt:
Assuming the application only recognizes volumes through environment variables, I commented out the OC_DATA_DIR variable in the .env file and added two direct volume bind mounts in docker-compose.yml.
docker-compose.yml:
volumes:
# primary data volume
- /var/lib/opencloud/opencloud-data:/var/lib/opencloud# new sda volume
- /var/lib/opencloud-sda/sda:/var/lib/opencloud-sda-data
This also did not work, and the new volume was not recognized by the application.
My goal is to use the new sda disk for additional data storage within OpenCloud, while keeping the existing sdb volume for the primary data.
Could you please advise on how to properly configure OpenCloud to recognize and use a second volume?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I have a question regarding how to configure additional data volumes in OpenCloud. I would appreciate it if you could provide some guidance.
My current setup is as follows:
I have installed OpenCloud in a Docker container on a Proxmox host. The application is running very well. I recently added a new disk to my system and successfully configured it as an LVM-Thin volume. The disk is visible and accessible from within the OpenCloud container at the path
/var/lib/opencloud-sda/sda
.I have attempted to configure this new disk as an additional volume using the following methods, but they have not worked:
My current
docker-compose.yml
and.env
files are configured to use a primary data volume defined by theOC_DATA_DIR
environment variable.First attempt:
I added a new bind mount directly to
docker-compose.yml
to make the new volume available to the container.docker-compose.yml:
With this setup, the new volume was not recognized by OpenCloud.
Second attempt:
Assuming the application only recognizes volumes through environment variables, I commented out the
OC_DATA_DIR
variable in the.env
file and added two direct volume bind mounts indocker-compose.yml
.docker-compose.yml:
This also did not work, and the new volume was not recognized by the application.
My goal is to use the new
sda
disk for additional data storage within OpenCloud, while keeping the existingsdb
volume for the primary data.Could you please advise on how to properly configure OpenCloud to recognize and use a second volume?
Beta Was this translation helpful? Give feedback.
All reactions