-
|
I'm trying to install OpenCloud as a separate Docker Container on an openmediavault system. I've made sure to copy the opencloud-compse directory structure and files to my OMV Docker share 'appdata' The OpenCloud log indicates that there's an issue with access to /etc/opencloud/opencloud.yaml: Using WinSCP I can tell that there is no directory /etc/opencloud for this file opencloud.yaml.
|
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 10 replies
-
|
The 1. Why
|
Beta Was this translation helpful? Give feedback.
-
|
Ooh, that's an elaborate response. Thank you very much for this. I will go through your suggestions tomorrow and hope to get a bit further. After all I managed with Sync-in as well. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks again @faketut for the elaborate asnwer. It was indeed the root ownership of the directory /appdata/opencloud-compose/config/opencloud that was the barrier. I was able to overcome that easily with WinSCP. |
Beta Was this translation helpful? Give feedback.
-
|
Ha! same issue with the storage directory share 'data'/opencloud |
Beta Was this translation helpful? Give feedback.
-
|
Yep, same fix — sudo chown -R 1000:100 /srv/dev-disk-by-uuid-44084fb3-1fd0-4bea-a166-e0c5427b10f5/opencloud(Adjust to whatever One thing worth double-checking, though: the log line you posted earlier says "storage directory is not a directory", which is subtly different from the previous "permission denied". That message means JetStream found a file at the path it expects to be a directory. So before just chowning, run: ls -ld /srv/dev-disk-by-uuid-44084fb3-1fd0-4bea-a166-e0c5427b10f5/opencloud
Since the first boot half-initialised things, I'd also recommend wiping the data dir before retrying so docker compose down
sudo rm -rf /srv/dev-disk-by-uuid-44084fb3-1fd0-4bea-a166-e0c5427b10f5/opencloud
sudo mkdir -p /srv/dev-disk-by-uuid-44084fb3-1fd0-4bea-a166-e0c5427b10f5/opencloud
sudo chown -R 1000:100 /srv/dev-disk-by-uuid-44084fb3-1fd0-4bea-a166-e0c5427b10f5/opencloud
docker compose up -dSame applies to any other host paths in your |
Beta Was this translation helpful? Give feedback.
-
|
Ooh, that's more advanced stuff you're guiding me towards. Slowly taking things in. |
Beta Was this translation helpful? Give feedback.
-
For clarity, my (updated) compose: |
Beta Was this translation helpful? Give feedback.
-
|
This is just too weird. I'm wiping /config/opencloud and restarting my openmediavault system |
Beta Was this translation helpful? Give feedback.
-
|
And now my Nginx Proxy Manager has fallen over Nginx Proxy Manager Compose log: Somewhere in my opencloud experiments I must have mislaid my port 80. |
Beta Was this translation helpful? Give feedback.
-
|
You're chasing two different problems now — let's split them. 1. The "is a directory" errors are the same bug I flagged beforeLook at the log: - ${{ sf:"appdata" }}/opencloud-compose/config/opencloud/banned-password-list.txt:/etc/opencloud/banned-password-list.txt
- ${{ sf:"appdata" }}/opencloud-compose/config/opencloud/csp.yaml:/etc/opencloud/csp.yaml
- ${{ sf:"appdata" }}/opencloud-compose/config/opencloud/proxy.yaml:/etc/opencloud/proxy.yamlWhen Docker starts the container and the host path doesn't exist yet, it auto-creates it as a directory so the bind mount can succeed. From then on, OpenCloud sees a directory where it expects a file, and you get exactly the error you're seeing. Wiping Fix, in order:
Same applies to The repeated 2. Is OMV the problem?Partly. Your compose still has these: user: ${{ uid:"appuser" }}:${{ gid:"users" }}
PUID: ${{ uid:"appuser" }}
...
${{ sf:"appdata" }}/opencloud-compose/config/opencloudThat docker compose configIf the output still shows literal user: "1000:100"
environment:
PUID: "1000"
PGID: "100"
TZ: "Europe/Amsterdam"
volumes:
- /srv/.../appdata/opencloud-compose/config/opencloud:/etc/opencloud
- /srv/.../data/opencloud:/var/lib/opencloud(Use the real absolute paths from 3. Port 80 / NPMThat's unrelated to OpenCloud's config — something else is now bound to sudo ss -ltnp | grep ':80 '
# or
sudo lsof -iTCP:80 -sTCP:LISTENMost likely culprits after your experiments:
Whatever TL;DR
|
Beta Was this translation helpful? Give feedback.
-
|
Thank you for being VERY patient with me, @faketut I do remember having done something with www-data at some point when I was following the OpenCloud Docker or Docker Compose installation guide. I need to revisit that. |
Beta Was this translation helpful? Give feedback.
-
|
Yes there it is: in OpenCloud Docs - Behind External Proxy there's an instruction to create a file /etc/nginx/sites-available/certbot-challenge, which I did, but I failed to obtain the SSL certificates, because certbot is not included in OMV. I need to remove that file and reload nginx. |
Beta Was this translation helpful? Give feedback.
-
|
Not quite: I guess that I need to also remove /etc/nginx/sites-enabled/certbot-challenge |
Beta Was this translation helpful? Give feedback.
-
|
Yes: No luck with opening Nginx Proxy Manager on the local network.... Ah, I needed to UP the Nginx Proxy Manager again. Yes that issue is resolved now. |
Beta Was this translation helpful? Give feedback.
-
|
Okay! We've past that first bridge. I'm in OpenCloud as admin.
|
Beta Was this translation helpful? Give feedback.
The
permission deniedis the only real blocker — everything below theCould not create config:line is just OpenCloud complaining that, because it couldn't writeopencloud.yaml, it never got ajwt_secret. Fix the write permission and the rest goes away. But your compose file has three separate issues stacked on top of each other, so let me unpack them.1. Why
/etc/opencloud/opencloud.yamlcan't be createdInside the container,
/etc/opencloudis your bind mount:- ./config/opencloud:/etc/opencloudSo the container is really trying to write to
./config/opencloud/opencloud.yamlon the host. The container is running as UID1000/ GID100, but the host directory was created by root (or by OMV'…