Nextcloud Container fails to install/ "up"

So, I keep getting this error, and error tells me there is no file "Couldn't find env file". I mean, duh, I am doing a fresh install. How could it not find a file it has not created yet?

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; docker-compose --file '/srv/dev-disk-by-uuid-b92f138b-3bc4-41c7-8b74-d22703a90420/Docker/docker/containers//nextcloud/nextcloud.yml' --env-file '/srv/dev-disk-by-uuid-b92f138b-3bc4-41c7-8b74-d22703a90420/Docker/docker/containers//nextcloud/nextcloud.env' up -d 2>&1': Couldn't find env file: /srv/dev-disk-by-uuid-b92f138b-3bc4-41c7-8b74-d22703a90420/Docker/docker/containers/nextcloud/nextcloud.env

OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; docker-compose --file '/srv/dev-disk-by-uuid-b92f138b-3bc4-41c7-8b74-d22703a90420/Docker/docker/containers//nextcloud/nextcloud.yml' --env-file '/srv/dev-disk-by-uuid-b92f138b-3bc4-41c7-8b74-d22703a90420/Docker/docker/containers//nextcloud/nextcloud.env' up -d 2>&1': Couldn't find env file: /srv/dev-disk-by-uuid-b92f138b-3bc4-41c7-8b74-d22703a90420/Docker/docker/containers/nextcloud/nextcloud.env in /usr/share/openmediavault/engined/rpc/compose.inc:429
Stack trace:
#0 /usr/share/php/openmediavault/rpc/serviceabstract.inc(619): OMVRpcServiceCompose->{closure}('/tmp/bgstatuseh...', '/tmp/bgoutputpA...')
#1 /usr/share/openmediavault/engined/rpc/compose.inc(432): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
#2 [internal function]: OMVRpcServiceCompose->doCommand(Array, Array)
#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#4 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('doCommand', Array, Array)
#5 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Compose', 'doCommand', Array, Array, 1)
#6 {main}

version: "2.1"
services:
  nextcloud:
    image: lscr.io/linuxserver/nextcloud:latest
    container_name: nextcloud
    environment:
      - PUID=1000
      - PGID=100
    volumes:
      - /srv/dev-disk-by-uuid-b92f138b-3bc4-41c7-8b74-d22703a90420/Docker/docker/containers/nextcloud:/config
      - /srv/dev-disk-by-uuid-b92f138b-3bc4-41c7-8b74-d22703a90420/Docker/docker/containers/nextcloud:/data
    ports:
      - 9443:443
    restart: unless-stopped

Done via Services : Compose : Files : create, cut n paste then UP

I F you not, for fun I changed all nextcloud instances with Nextcloud, and it installed just fine, WTF is with that? Now I gotta worry about caps?

I will start in reverse. The weird folder was because prior to the latest move/update with the omv-extras change, and my not knowing all what was going on in the beginning, I had a /Docker directory and then a /Container directory. When I tried to make the share directory it said I had to create a new directory, so, and I don't know why, I did Docker/docker/containers. It just is what it is.

Timezone not set, my bad, not sure why I missed it.

Database, this I am unsure of, I have never created a database... I just log in and create users, worked fine. What is the benefit of doing so?

As far as the SWAG /Nextcloud you mentioned, I am/was using it through NGINX. I have had no issues. My issue was it was working beautifully until it did not. Tried everything to repair it, would not, so I deleted it. I ran the SAME compose I did back when it did work, and that was the error I initially posted on.. It error'd out. So, for shyts n giggles I changed the lowercase nextcloud to Nextcloud, and the compose worked. Why? maybe a freak accident, I could not tell you. The compose I pasted earlier is the one I have always used. As far as sqllite,it is for 1 user, me, which was why i left it default.

I read enough originally to get it all working flawlessly with nginx so I was content. I could not tell you why it messed up, maybe random got corrupt.

As far as having confidence in moving the directories, sure, wtf not, but I would also like to know the logistics behind it?

OMV Docker is set to '/srv/dev-disk-by-uuid-b92f138b-3bc4-41c7-8b74-d22703a90420/Docker/docker' (man I don't know why the 2 docker directories, it works, would that make it not work?) and my "share" directory is 'Conpose [on /dev/sdc1, Docker/docker/containers/]'

Zitat von matdb

So everything is working correctly again?

Just the error about the .env file and after changing "nextcloud" to "Nextcloud" it worked.

Probably because the .en file was created is suspect.

If it works and you are fine how it is then leave it like this.

(Hopefully that doesn't sound bad or aggressive not the intension to!!!)

What do you mean by this?

Alles anzeigen

You had mentioned that if I have the confidence to do so, which I understand if I feel comfortable, you mentioned to move the directory. I know mine was a bit weird, Docker/docker/containers but I was wondering what the reason would be, other than cleaning up the weird redundant directory structure.

And no offense as all you've been a great help. I'm Sicilian, I always speak as if it is our last meal. To the point.

Fair enough. Thank you Sir.