Nextcloud with Letsencrypt using OMV and docker-compose - Q&A

Zoki · 5. Dezember 2021

For those who would like to follw the roue of bind mounting the docker directory:

Stop the docker daemon
Chose a directory where you future docker root should be /path_to_my_new_docker_root
Make sure /path_to_my_new_docker_root is not on a mergerfs
for testing purposes: do a bind mount from /var/lob/docker to /path_to_my_new_docker_root (testing only)
Start your docker deamon and check docker image ls -> no image should be found!
Stop the docker daemon
unmount /var/lib/docker again
Check the contents of /path_to_my_new_docker_root -> the docker files should be there
now remove all files in /path_to_my_new_docker_root
Now you are prepared for the real thing
Stop the docker daemon again
Move the content of /var/lib/docker to /path_to_my_new_docker_root (or do a rsync -a ... to keep the old stuff)
append a line to /etc/fstab
/path_to_my_new_docker_root /var/lib/docker none bind 0 0
Start the docker daemon and check docker image ls and docker volume ls and docker ps -a
All your stuff should be there and the containers be running.
Reboot and check again
If everything works click the link in my signature

Nefertiti · 5. Dezember 2021

Honestly I am pretty sure I was booting from the new drive since I was trying to wipe the old one

/dev/nvme0n1 is the new

/dev/nvme1n1 was the old

Zoki · 5. Dezember 2021

But booting from the other disk is the only thing which makes sense when looking at the errors you posted.

Files changing on disk after booting ....

Nefertiti · 5. Dezember 2021

Zitat von Zoki

If everything works click the link in my signature

Thank you for the detailed info not sure what you are trying to get but this paypal link is not even working

https://www.paypal.com/donate?…Q0aIMjVZDxJaD8A2HZ7OdwrT-

Nefertiti · 5. Dezember 2021

Zitat von Zoki

But booting from the other disk is the only thing which makes sense when looking at the errors you posted.
Files changing on disk after booting ....

Probably right something got messed up in grub

KM0201 · 5. Dezember 2021

Zitat von Zoki

For those who would like to follw the roue of bind mounting the docker directory:

Stop the docker daemon
Chose a directory where you future docker root should be /path_to_my_new_docker_root
Make sure /path_to_my_new_docker_root is not on a mergerfs
for testing purposes: do a bind mount from /var/lob/docker to /path_to_my_new_docker_root (testing only)
Start your docker deamon and check docker image ls -> no image should be found!
Stop the docker daemon
unmount /var/lib/docker again
Check the contents of /path_to_my_new_docker_root -> the docker files should be there
now remove all files in /path_to_my_new_docker_root
Now you are prepared for the real thing
Stop the docker daemon again
Move the content of /var/lib/docker to /path_to_my_new_docker_root (or do a rsync -a ... to keep the old stuff)
append a line to /etc/fstab
/path_to_my_new_docker_root /var/lib/docker none bind 0 0
Start the docker daemon and check docker image ls and docker volume ls and docker ps -a
All your stuff should be there and the containers be running.
Reboot and check again
If everything works click the link in my signature

Basically the same as I suggested.. which worked until the second OS drive came into play.

Nefertiti · 5. Dezember 2021

Zitat von Zoki

But booting from the other disk is the only thing which makes sense when looking at the errors you posted.
Files changing on disk after booting ....

Probably right something got messed up in grub

Zoki · 5. Dezember 2021

Zitat von Nefertiti

Thank you for the detailed info not sure what you are trying to get but this paypal link is not even working
https://www.paypal.com/donate?…Q0aIMjVZDxJaD8A2HZ7OdwrT-

Take this one instead: https://www.openmediavault.org/?page_id=1149

KM0201 · 5. Dezember 2021

Zitat von Nefertiti

Probably right something got messed up in grub

So I guess I'm curious now if that resolved your Nvidia issue, even though your containers are not on the OS drive anymore?

I'm assuming it did.

Nefertiti · 5. Dezember 2021

It was not a so called issue except it was impossible to have doker on a data drive and nvidia working since if you were moving the docker thru the usual way you had to changed the docker etc/docker /daemon.json to

{

"runtimes": {

"nvidia": {

"path": "/usr/bin/nvidia-container-runtime",

"runtimeArgs": []

}

},

"default-runtime": "nvidia"

}

And in this case doker went back to var lib

Although right now the nividia runtime is not working with OMV 6 except there is a way to make it work Nvidia working with OMV 6

Yes it is resolved

Starbuck1973 · 7. Dezember 2021

Zitat von KM0201

LOL.. You guys are gonna love Starbucks problem... we are finishing it up now... I don't think we'd have ever figured htis out (or I wouldn't have.. he wasn't getting a key)

I am documenting everything, screenshots and so on. How can I share my guide? Directly here?

Zitat von KM0201
One final thing for you guys running duckdns. IF YOU DO NOT HAVE A STATIC PUBLIC IP ADDRESS... (or even if you do, this won't hurt)... use this compose file in a stack and adjust as needed. This will basically allow your duckdns profile to be automatically updated if your public IP ever changes... thus keeping your services online. Just adjust the lines with the # and then remove that #
Code
version: "2.1"
services:
  duckdns:
    image: ghcr.io/linuxserver/duckdns
    container_name: duckdns
    environment:
      #- PUID=1000
      #- PGID=1000
      #- SUBDOMAINS=your_subdomain
      #- TOKEN=your_token
      - LOG_FILE=false
    volumes:
       - /etc/localtime:/etc/localtime:ro
      #- /NAS/AppData/duckdns:/config
    restart: unless-stopped
Alles anzeigen

following your guide, subdomains=wildcard, right?

Soma · 7. Dezember 2021

Zitat von Starbuck1973

I am documenting everything, screenshots and so on. How can I share my guide? Directly here?
following your guide, subdomains=wildcard, right?

If you mean on the duckdns YML quoted, NO.

It is the subdomain you registered on duckdns:

Code

SUBDOMAINS=mysite.duckdns.org

Starbuck1973 · 7. Dezember 2021

Zitat von Soma
If you mean on the duckdns YML quoted, NO.

It is the subdomain you registered on duckdns:
Code
SUBDOMAINS=mysite.duckdns.org

OK, I ask because in swag stack

Code

SUBDOMAINS=wildcard

Thanks

KM0201 · 7. Dezember 2021

Zitat von Starbuck1973

I am documenting everything, screenshots and so on. How can I share my guide? Directly here?
following your guide, subdomains=wildcard, right?

No, that is only if you're using duckdns.... (note that is a duckdns contaiiner).. so that needs to be your subdomain. That container is so your IP will be updated if it changes.

In swag.. the "wildcard" if you use duckdns.. isn't your duckdns subdomain (that is defined in the URL= of swag).. it's technically whatever service you are using (nextcloud.duckdns... airsonic.duckdns... etc.)

KM0201 · 7. Dezember 2021

Starbuck1973 I'll try to figure out a way to make that more clear tomorrow.. in the duckdns container, it is JUST your subdomain you registered w/ duckdns.. not the full URL.

swag and duckdns are completely different containers in how they deal w/ subdomains. The duckdns container isn't even 100% required.. it's just if your IP changes.. and it isn't updated in the IP on your duckdns management page.. all your services will go down until you manually update it. This container, just manually makes sure that the IP of your server and the IP address pointing at your duckdns domain.. stay the same.

KM0201 · 7. Dezember 2021

Zitat von Starbuck1973

I am documenting everything, screenshots and so on. How can I share my guide? Directly here?
following your guide, subdomains=wildcard, right?

By the way "your guide" is exactly what I put there in that thread.. your biggest problem.. was your github login to duckdns was not allowing swag to fetch a cert. As I think we finally figured out.. the swag container will only grant a cert if you're using a gmail login to duckdns... as once you logged in to duckdns w/ your gmail account and set up a subdomain, you got a cert no problem and the rest of that guide was fine.

openmedianer · 17. Februar 2022

Hello macom , did you can write you last edit in your first post?

Thema

[How-To] Nextcloud with swag (Letsencrypt) using OMV and docker-compose

Docker Container set up by this method can be managed by Portainer or from CLI.

Pre-requisites
In order to be able to reach nextcloud from the internet you need an external IPv4 address and a hostname.
Regarding external IPv4 address check you router or ask your internet service provider.
To register a hostname you can use services like duckdns, selfhost.eu, strato.de or many others.
Make sure to use strong passwords!!!

Preparation

Install and fully update OMV (a restart might be needed if the kernel

…

macom

10. August 2019

I'm only find "Aug 10th 2019".

Thank you, for your nice work.

Best regards

openmedianer

KM0201 · 17. Februar 2022

Zitat von openmedianer

Hello macom , did you can write you last edit in your first post?

Thema

[How-To] Nextcloud with swag (Letsencrypt) using OMV and docker-compose

Docker Container set up by this method can be managed by Portainer or from CLI.

Pre-requisites
In order to be able to reach nextcloud from the internet you need an external IPv4 address and a hostname.
Regarding external IPv4 address check you router or ask your internet service provider.
To register a hostname you can use services like duckdns, selfhost.eu, strato.de or many others.
Make sure to use strong passwords!!!

Preparation

Install and fully update OMV (a restart might be needed if the kernel
…

macom

10. August 2019

I'm only find "Aug 10th 2019".

Thank you, for your nice work.

Best regards
openmedianer

Alles anzeigen

What are you referring to? To my knowledge he's the only one who's ever edited that post

Soma · 17. Februar 2022

Zitat von openmedianer

Hello macom , did you can write you last edit in your first post?

Thema

[How-To] Nextcloud with swag (Letsencrypt) using OMV and docker-compose

Docker Container set up by this method can be managed by Portainer or from CLI.

Pre-requisites
In order to be able to reach nextcloud from the internet you need an external IPv4 address and a hostname.
Regarding external IPv4 address check you router or ask your internet service provider.
To register a hostname you can use services like duckdns, selfhost.eu, strato.de or many others.
Make sure to use strong passwords!!!

Preparation

Install and fully update OMV (a restart might be needed if the kernel
…

macom

10. August 2019

I'm only find "Aug 10th 2019".

Thank you, for your nice work.

Best regards
openmedianer

Alles anzeigen

Last edited (Dec 30th 2021) so it still is recently edited.

Code

Edited 21 times, last by macom: corrected "depends on" (mariadb); put the correct names of the fields on the Welcome page of Nextcloud to specify the MySQL/MariaDB added Q&A link removed exposed ports of nextcloud as not needed added SWAG replaced letsencrypt by swag (Dec 30th 2021)

openmedianer · 17. Februar 2022

Soma

Last edited (Dec 30th 2021) so it still is recently edited.

Where did you have find this Information?

Greets

openmedianer

Jetzt mitmachen!