Need help to install Nextcloud with Docker and Portainer

Tuxus · Dec 9th 2019

Hello, after my OMV 4 installation was lost due to hard drive crashes, I took the opportunity to upgrade the hardware and install OMV 5. This went smoothly and quickly and the configuration (drives, users, shares, dlna) went smoothly.
Now I have discovered that Docker works with a portainer or cockpit. Is that correct?
Cockpit makes a mistake while trying to install.
Portainer can be started properly.

Now I just need a tutorial to cleanly install Nextcloud in this new environment. Unfortunately I find only OMV 4 (Docker) instructions. Unfortunately, no instructions for OMV 5.

Can someone please give me a hint for a guide or take something here by the hand?

Docker is running. Portainer is running.
I only need Nextcloud for the local network. A release on the Internet is not planned.

Thank you very much.

Code

System:    Host: omvnas.fritz.box Kernel: 5.3.0-0.bpo.2-amd64 x86_64 bits: 64 Console: tty 0           


Distro: Debian GNU/Linux 10 (buster)


Machine:   Type: Desktop Mobo: Gigabyte model: B85M-HD3 v: x.x serial: N/A BIOS: American Megatrends v: FD date: 03/28/2014


CPU:       Topology: Quad Core model: Intel Core i5-4440 bits: 64 type: MCP L2 cache: 6144 KiB           Speed: 799 MHz min/max: 800/3300 MHz Core speeds (MHz): 1: 798 2: 798 3: 798 4: 798


Graphics:  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics driver: i915 v: kernel           


Audio:     Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio driver: snd_hda_intel           Device-2: Intel 8 Series/C220 Series High Definition Audio driver: snd_hda_intel           Sound Server: ALSA v: k5.3.0-0.bpo.2-amd64


Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169           IF: enp2s0 state: up speed: 1000 Mbps duplex: full mac: <filter>           IF-ID-1: docker0 state: up speed: N/A duplex: N/A mac: <filter>           IF-ID-2: vethf25d8d9 state: up speed: 10000 Mbps duplex: full mac: <filter>


Drives:    Local Storage: total: 11.03 TiB used: 1.52 TiB (13.8%)           
ID-1: /dev/sda vendor: Intenso model: SSD Sata III size: 119.24 GiB           
ID-2: /dev/sdb vendor: Toshiba model: DT01ACA300 size: 2.73 TiB           
ID-3: /dev/sdc vendor: Toshiba model: DT01ACA300 size: 2.73 TiB           
ID-4: /dev/sdd vendor: Toshiba model: DT01ACA300 size: 2.73 TiB           
ID-5: /dev/sde vendor: Toshiba model: DT01ACA200 size: 1.82 TiB           
ID-6: /dev/sdf vendor: Toshiba model: DT01ACA100 size: 931.51 GiB


Partition: ID-1: / size: 105.17 GiB used: 2.72 GiB (2.6%) fs: ext4 dev: /dev/sda1           ID-2: swap-1 size: 11.88 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda5

Display More

Tuxus · Dec 9th 2019

I just found this here https://forum.openmediavault.o…g-OMV-and-docker-compose/
It seems this is right for me to learn and try?

Morlan · Dec 9th 2019

Yes. You can also enter the docker-compose.yml as a stack in portainer.

Tuxus · Dec 9th 2019

Oh thanks for the info.

Tuxus · Dec 10th 2019

Quote from Morlan

Yes. You can also enter the docker-compose.yml as a stack in portainer.

There is a field Web editor . I think there should paste the source-code from https://forum.openmediavault.o…g-OMV-and-docker-compose/ .
I would like to use Nextcloud in my local network without internet connection. Can I delete the part with Letsencrypt before I take over the code? I think also there is no portforwarding needed in my case.
Which volumes are right for nextcloud- and mariadb-services? Should the volumes are the same to /home/dockeruser/nextcloud or can i set volume of my choice?

Thanks for support.

Morlan · Dec 10th 2019

Quote from Tuxus

There is a field Web editor . I think there should paste the source-code from forum.openmediavault.org/index…g-OMV-and-docker-compose/ .

Yes.

Quote from Tuxus

I would like to use Nextcloud in my local network without internet connection. Can I delete the part with Letsencrypt before I take over the code?

Yes. Take the example below:

Code: docker-compose.yml

version: "2"
services:
  nextcloud:
    image: linuxserver/nextcloud
    container_name: nextcloud
    environment:
      - PUID=1000 #change PUID if needed
      - PGID=100  #change PGID if needed
      - TZ=Europe/Berlin #change Time Zone if needed
    volumes:
      - /srv/dev-disk-by-label-disk1/appdata/nextcloud/config:/config #/srv/dev-disk-by-label-disk1 needs to be adjusted
      - /srv/dev-disk-by-label-disk1/appdata/nextcloud/data:/data     #/srv/dev-disk-by-label-disk1 needs to be adjusted
    depends_on:
      - mariadb
    ports: # uncomment this and the next line if you want to bypass the proxy
      - 450:443
    restart: unless-stopped
  mariadb:
    image: linuxserver/mariadb
    container_name: nextclouddb
    environment:
      - PUID=1000 #change PUID if needed
      - PGID=100  #change PGID if needed
      - MYSQL_ROOT_PASSWORD=mariadbpassword  #change password
      - TZ=Europe/Berlin #Change Time Zone if needed
    volumes:
      - /srv/dev-disk-by-label-disk1/appdata/nextclouddb:/config    #/srv/dev-disk-by-label-disk1 needs to be adjusted
    restart: unless-stopped

Display More

Quote from Tuxus

I think also there is no portforwarding needed in my case.

If you mean from your router then you are correct.

Quote from Tuxus

Which volumes are right for nextcloud- and mariadb-services? Should the volumes are the same to /home/dockeruser/nextcloud or can i set volume of my choice?

You can set the volumes of your choice. If your OMV is running from a SD-Card dont your SD card for neither config nor data directories.

_____________________________________________________________________________________________

After deployment of the docker with Portainer you can find the Nextcloud-GUI under https://yourhostip:450 (trust the untrusted SSL-Certificate). Then skip directly to the section:

Quote from macom

on the welcome screen of nextcloud we need to configure the database

click on "Storage&Database"

select MySQL/MariaDB

Database user --> "root"

Database password --> password which has been specified in the docker-compose file with MYSQL_ROOT_PASSWORD

Database name --> "nextcloud"

localhost host --> "nextclouddb"
then click "finish setup"

Display More

Tuxus · Dec 10th 2019

I'll try this. Thanks for your help.

Tuxus · Dec 10th 2019

I try'd it with:

Code

version: "2"
services:
  nextcloud:
    image: linuxserver/nextcloud
    container_name: nextcloud
    environment:
      - PUID=1001 #PUID dockeruser
      - PGID=100  #change PGID if needed
      - TZ=Europe/Berlin #change Time Zone if needed
    volumes:
      - /srv/dev-disk-by-label-netzwerkdaten/appdata/nextcloud/config:/config #/srv/dev-disk-by-label-disk1 needs to be adjusted
      - /srv/dev-disk-by-label-netzwerkdaten/appdata/nextcloud/data:/data     #/srv/dev-disk-by-label-disk1 needs to be adjusted
    depends_on:
      - mariadb
    ports: # uncomment this and the next line if you want to bypass the proxy
     - 450:443
    restart: unless-stopped
  mariadb:
    image: linuxserver/mariadb
    container_name: nextclouddb
    environment:
      - PUID=1001 #PUID of dockeruser
      - PGID=100  #change PGID if needed
      - MYSQL_ROOT_PASSWORD=myownpassword  #change password
      - TZ=Europe/Berlin #Change Time Zone if needed
    volumes:
      - /srv/dev-disk-by-label-netzwerkdaten/appdata/nextclouddb:/config    #/srv/dev-disk-by-label-disk1 needs to be adjusted
    restart: unless-stopped

Display More

and i run into:

Deployment errorError response from daemon:Get https://registry-1.docker.io/v2/:dial tcp:lookupregistry-1.docker.io on [::1]:53:read udp [::1]:38163->[::1]:53:read: connection refused

photo_2019-12-10_22-41-55.jpg

Tuxus · Dec 10th 2019

I try'd it with:

Code

version: "2"
services:
  nextcloud:
    image: linuxserver/nextcloud
    container_name: nextcloud
    environment:
      - PUID=1001 #PUID dockeruser
      - PGID=100  #change PGID if needed
      - TZ=Europe/Berlin #change Time Zone if needed
    volumes:
      - /srv/dev-disk-by-label-netzwerkdaten/appdata/nextcloud/config:/config #/srv/dev-disk-by-label-disk1 needs to be adjusted
      - /srv/dev-disk-by-label-netzwerkdaten/appdata/nextcloud/data:/data     #/srv/dev-disk-by-label-disk1 needs to be adjusted
    depends_on:
      - mariadb
    ports: # uncomment this and the next line if you want to bypass the proxy
     - 450:443
    restart: unless-stopped
  mariadb:
    image: linuxserver/mariadb
    container_name: nextclouddb
    environment:
      - PUID=1001 #PUID of dockeruser
      - PGID=100  #change PGID if needed
      - MYSQL_ROOT_PASSWORD=myownpassword  #change password
      - TZ=Europe/Berlin #Change Time Zone if needed
    volumes:
      - /srv/dev-disk-by-label-netzwerkdaten/appdata/nextclouddb:/config    #/srv/dev-disk-by-label-disk1 needs to be adjusted
    restart: unless-stopped

Display More

and i run into:

Code

Deployment errorError response from daemon:Get https://registry-1.docker.io/v2/:dial tcp:lookupregistry-1.docker.io on [::1]:53:read udp [::1]:38163->[::1]:53:read: connection refused

photo_2019-12-10_22-41-55.jpg

gderf · Dec 10th 2019

If you do not have an active IPV6 connection with your ISP you should disable IPV6 in OMV's Network configuration.

Tuxus · Dec 10th 2019

IPV6 is already disabled from beginning.

I see in this case that http-proxy is disabled in OMV. Is that right or should be enabled?

gderf · Dec 10th 2019

I do not have IPV6 enabled in OMV, I have no IPV6 connection configured with my ISP, and the http-proxy is disabled in OMV. I never see see messages like you are seeing.

Run the ip address command and verify that there are no IPV6 addresses configured, including link locals.

Tuxus · Dec 10th 2019

Code

ip address show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 74:d4:35:ea:40:42 brd ff:ff:ff:ff:ff:ff
    inet 192.168.178.xx/24 brd 192.168.178.255 scope global dynamic enp2s0
       valid_lft 856894sec preferred_lft 856894sec

Display More

Tuxus · Dec 10th 2019

I see in portainer there is no user or group (except admin) created. I think i should create them. Or is it unnecessary when i deploy the stack as Administrators ? Is this right or should i deploy the stack Restricted to e set of user/teams ?

gderf · Dec 11th 2019

I don't play with those settings, I leave them as I found them.

Tuxus · Dec 11th 2019

Okay. Maybe someone has an idea. In the meantime I will try to find out where the mistake could be ...
I am not sure, but under OMV 4 you had to create Nextcloud in a container. Why now as a stack and not as a container under OMV 5?

gderf · Dec 11th 2019

Deploying a stack creates the container for you.

Tuxus · Dec 11th 2019

Okay. Now only the error would have to be discovered. I just noticed that at:

Code

sudo apt update && sudo apt dist-upgrade

in OMV the output is:

Code

Get: 1 file: / var / cache / openmediavault / archives InRelease
Ign: 1 file: / var / cache / openmediavault / archives InRelease
Get: 2 file: / var / cache / openmediavault / archives Release
Ign: 2 file: / var / cache / openmediavault / archives Release
Get: 3 file: / var / cache / openmediavault / archives Packages
Ign: 3 file: / var / cache / openmediavault / archives packages
Error: 4 http://packages.openmediavault.org/public usul InRelease
  Packages.openmediavault.org could not be resolved.
Error: 5 https://openmediavault.github.io/packages usul InRelease
  "Openmediavault.github.io" could not be resolved.
Get: 6 file: / var / cache / openmediavault / archives Translation-de_DE
Ign: 6 file: / var / cache / openmediavault / archives Translation_en_US
Error: 7 http://linux.teamviewer.com/deb stable InRelease
  Linux.teamviewer.com could not be resolved.
Miss: 8 http://httpredir.debian.org/debian buster-backports InRelease
  "Httpredir.debian.org" could not be resolved.
Get: 9 file: / var / cache / openmediavault / archives Translation-de
Ign: 9 file: / var / cache / openmediavault / archives Translation de
Error: 10 https://dl.bintray.com/openmediavault-plugin-developers/usul buster InRelease
  Dl.bintray.com could not be resolved.
Error: 11 https://download.docker.com/linux/debian buster InRelease
  "Download.docker.com" could not be resolved.
Error: 12 https://dl.bintray.com/openmediavault-plugin-developers/usul-extras buster InRelease
  Dl.bintray.com could not be resolved.
Get: 13 file: / var / cache / openmediavault / archives Translation
Ign: 13 file: / var / cache / openmediavault / archives Translation
Ign: 3 file: / var / cache / openmediavault / archives packages
Get: 6 file: / var / cache / openmediavault / archives Translation-de_DE
Ign: 6 file: / var / cache / openmediavault / archives Translation_en_US
Get: 9 file: / var / cache / openmediavault / archives Translation-de
Ign: 9 file: / var / cache / openmediavault / archives Translation de
Wrong: 14 http://deb.debian.org/debian buster InRelease
  "Deb.debian.org" could not be resolved.
Miss: 15 http://security.debian.org/debian-security buster / updates InRelease
  "Security.debian.org" could not be resolved.
Miss: 16 http://deb.debian.org/debian buster-updates InRelease
  "Deb.debian.org" could not be resolved.
Get: 13 file: / var / cache / openmediavault / archives Translation
Ign: 13 file: / var / cache / openmediavault / archives Translation
Get: 3 file: / var / cache / openmediavault / archives Packages
Ign: 3 file: / var / cache / openmediavault / archives packages
Get: 6 file: / var / cache / openmediavault / archives Translation-de_DE
Ign: 6 file: / var / cache / openmediavault / archives Translation_en_US
Get: 9 file: / var / cache / openmediavault / archives Translation-de
Ign: 9 file: / var / cache / openmediavault / archives Translation de
Get: 13 file: / var / cache / openmediavault / archives Translation
Ign: 13 file: / var / cache / openmediavault / archives Translation
Get: 3 file: / var / cache / openmediavault / archives Packages
Ign: 3 file: / var / cache / openmediavault / archives packages
Get: 6 file: / var / cache / openmediavault / archives Translation-de_DE
Ign: 6 file: / var / cache / openmediavault / archives Translation_en_US
Get: 9 file: / var / cache / openmediavault / archives Translation-de
Ign: 9 file: / var / cache / openmediavault / archives Translation de
Get: 13 file: / var / cache / openmediavault / archives Translation
Ign: 13 file: / var / cache / openmediavault / archives Translation
Get: 3 file: / var / cache / openmediavault / archives Packages
Ign: 3 file: / var / cache / openmediavault / archives packages
Get: 6 file: / var / cache / openmediavault / archives Translation-de_DE
Ign: 6 file: / var / cache / openmediavault / archives Translation_en_US
Get: 9 file: / var / cache / openmediavault / archives Translation-de
Ign: 9 file: / var / cache / openmediavault / archives Translation de
Get: 13 file: / var / cache / openmediavault / archives Translation
Ign: 13 file: / var / cache / openmediavault / archives Translation
Get: 3 file: / var / cache / openmediavault / archives Packages
Ign: 3 file: / var / cache / openmediavault / archives packages
Get: 6 file: / var / cache / openmediavault / archives Translation-de_DE
Ign: 6 file: / var / cache / openmediavault / archives Translation_en_US
Get: 9 file: / var / cache / openmediavault / archives Translation-de
Ign: 9 file: / var / cache / openmediavault / archives Translation de
Get: 13 file: / var / cache / openmediavault / archives Translation
Ign: 13 file: / var / cache / openmediavault / archives Translation
Get: 3 file: / var / cache / openmediavault / archives Packages
Get: 6 file: / var / cache / openmediavault / archives Translation-de_DE
Ign: 6 file: / var / cache / openmediavault / archives Translation_en_US
Get: 9 file: / var / cache / openmediavault / archives Translation-de
Ign: 9 file: / var / cache / openmediavault / archives Translation de
Get: 13 file: / var / cache / openmediavault / archives Translation
Ign: 13 file: / var / cache / openmediavault / archives Translation
Package lists are read ... Done
Dependency tree is set up.
Status information is read .... Done
All packages are up to date.
W: Failed to get http://deb.debian.org/debian/dists/buster/InRelease "deb.debian.org" could not be resolved.
W: Failed to get http://security.debian.org/debian-security/dists/buster/updates/InRelease "security.debian.org" could not be resolved.
W: Failed to get http://deb.debian.org/debian/dists/buster-updates/InRelease "deb.debian.org" could not be resolved.
W: Failed to get https://dl.bintray.com/openmediavault-plugin-developers/usul/dists/buster/InRelease dl.bintray.com could not be resolved.
W: Failed to get https://download.docker.com/linux/debian/dists/buster/InRelease "download.docker.com" could not be resolved.
W: Failed to get http://linux.teamviewer.com/deb/dists/stable/InRelease linux.teamviewer.com could not be resolved.
W: Failure to get https://dl.bintray.com/openmediavault-plugin-developers/usul-extras/dists/buster/InRelease "dl.bintray.com" could not be resolved.
W: Failed to get http://httpredir.debian.org/debian/dists/buster-backports/InRelease "httpredir.debian.org" could not be resolved.
W: Failed to get http://packages.openmediavault.org/public/dists/usul/InRelease packages.openmediavault.org could not be resolved.
W: Failed to get https://openmediavault.github.io/packages/dists/usul/InRelease openmediavault.github.io could not be resolved.
W: Some index files could not be downloaded. They were ignored or old ones used in their place.
Package lists are read ... Done
Dependency tree is set up.
Status information is read .... Done
Package upgrade (upgrade) is calculated ... Done
0 updated, 0 reinstalled, 0 removed and 0 not updated.

Display More

It looks not very nice. I think there is a bug in the network settings...

Tuxus · Dec 11th 2019

I found the error. The network interface had changed from dhcp to docker. I don't know why. I fix it with omv-firstaid and the stack is working fine.
Now i'm trying to open nextcloud http://192.168..........:450/ and it says
400 Bad Request
The plain HTTP request was sent to HTTPS portnginx/1.16.1
Should i change the port 443 to 80 in the docker-compose.yml ?

gderf · Dec 11th 2019

I can't help you. I do not use Nextcloud.

Participate now!