La tua installazione Docker non utilizza un driver di storage supportato.

[pauln (Paul Nate)]

Ciao a tutti, ho un problema con un aggiornamento che mi restituisce il seguente messaggio:

Se desideri comunque procedere utilizzando il tuo driver di archiviazione non supportato,
leggi il codice sorgente del launcher e scopri come aggirare questo controllo.
root@sendy:/var/docker/discourse# git pull
Already up-to-date.
root@****:/var/docker/discourse# ./launcher rebuild app
La tua installazione Docker non utilizza un driver di archiviazione supportato. Se fossimo t.
overlay2 è il driver di archiviazione consigliato, sebbene zfs e aufs possano funzionare anch'essi.
Altri driver di archiviazione sono noti per essere problematici.
Puoi scoprire quale filesystem stai utilizzando eseguendo "docker info" e controllando.

Se desideri comunque procedere utilizzando il tuo driver di archiviazione non supportato,
leggi il codice sorgente del launcher e scopri come aggirare questo controllo.
root@****:/var/docker/discourse# docker info
Containers: 5
Images: 74
Storage Driver: devicemapper
 Pool Name: docker-8:0-1970634-pool
 Pool Blocksize: 65.54 kB
 Data file: /var/lib/docker/devicemapper/devicemapper/data
 Metadata file: /var/lib/docker/devicemapper/devicemapper/metadata
 Data Space Used: 34.15 GB
 Data Space Total: 107.4 GB
 Metadata Space Used: 41.37 MB
 Metadata Space Total: 2.147 GB
 Library Version: 1.02.82-git (2013-10-04)
Execution Driver: native-0.2
Kernel Version: 5.6.14-x86_64-linode135
Operating System: Debian GNU/Linux

[neounix (Dark Matter)]

Hi @pauln

If your host is only running Docker to support Discourse and your Linux kernel supports the OverlayFS, then I recommend you reconfigure Docker (carefully) to use the overlay2 storage driver.

Hope this helps.

[pauln (Paul Nate)]

Can you let me know how to do it?

I am running on Linode (Debian 7.5)

Can you tell me how to reconfigure Docker?

[Falco]

@pauln

Debian 7.5

Per official Docker docs:

To install Docker Engine, you need the 64-bit version of one of these Debian or Raspbian versions:

• Debian Buster 10 (stable)
• Debian Stretch 9 / Raspbian Stretch

I recommend using an updated VPS.

[neounix (Dark Matter)]

@pauln

Hey, I’m booted up and awake.

What do you want to do?

Do you want to move to a more recent version of Debian or do you want me to see if I can get your 7.5 working first?

If you want me to see if I can get your 7.5 version working; I need to know:

• Is Docker running anything else?

The issue is that when you change the Docker storage driver in the Docker config file; all existing containers will not be accessible; so we will need to:

• Make sure you have a full Discourse backup (always)

• Shutdown Docker.

• Edit the Docker config to change the storage driver.

• Restart Docker

• Rebuild Discourse

If your Debian kernel supports OverlayFS, this will go smoothly. If not, it will fail, but no harm done, we can revert back to devicemapper.

Let me know how you wish to proceed.

Thanks.

[pauln (Paul Nate)]

Yes I would like to get it working on 7.5 first. Docker is only running Discourse.

Thank you lets do it

[neounix (Dark Matter)]

@pauln

Yes I would like to get it working on 7.5 first. Docker is only running Discourse.

Thank you lets do it

OK… that’s what I thought

Actually, the steps are outlined here:

Use the OverlayFS storage driver

Take a quick look and let me know if you are OK with the steps outlined or if you have any questions.

Thanks.

[pauln (Paul Nate)]

OK let me try this steps and get back to you? I did try similar and it did not work. Will keep you posted

[neounix (Dark Matter)]

@pauln

OK let me try this steps and get back to you? I did try similar and it did not work. Will keep you posted

If your Linux kernel does not support the OverlayFS, it will fail.

No worries.

You can revert back

If it does not fail, then I can go back to sleep

[pauln (Paul Nate)]

How can i test if it does support or not?

[neounix (Dark Matter)]

Docker will not restart.

In other words, step 5 in the Docker instructions (above) will fail:

5. Start Docker.

$ sudo systemctl start docker

This will either fail or succeed…

(you might need a different command other than systemctl , but the concept is the same)

[pauln (Paul Nate)]

Ok trying. Will post update here

[neounix (Dark Matter)]

Have fun.

I will not have a coffee, hoping for a miracle and that your old Linux kernel (for some odd reason) actually supports OverlayFS.

My quick “Google” on this, was not encouraging, to be honest, but I’m trying to be optimistic.

[pauln (Paul Nate)]

Did not work. How would I move my Forum to new VPS not losing all the user data?

[Stephen]

Download your app.yml and the most recent backup.

Your app.yml is typically in /var/discourse/containers

The backups are in /var/discourse/shared/CONTAINERNAME/backups

If your discourse site is inaccessible they can still be downloaded via SFTP or using SCP.

[neounix (Dark Matter)]

Hi @pauln

Sorry to hear that. I suspected your old kernel did not support OverlayFS, but it rarely hurts to try and learn things along the way.

Do you want to stick with Debian or go for Ubuntu on your new setup?

I have used Ubuntu “forever” and it is officially supported by Discourse, so that is my recommendation, but of course, the choice is up to you. Debian is cool too

[neounix (Dark Matter)]

@pauln

Did not work. How would I move my Forum to new VPS not losing all the user data?

Hey @pauln

There are a herd of people who can help you spin up a new VPS and install Discourse from scratch and restore your site; so I’m going to go back to sleep.

Nice working with you. In closing, here is my recommendation:

• Spin up a new Linode Ubuntu VPS, since you are already a Linode user (like me, BTW).
• Install Discourse from scratch (well documented)
• Restore Discourse from your backup (well documented)

There are a lot of talented folks to guide you along this journey, so I’m signing off for now.

Best wishes.

[neounix (Dark Matter)]

Good Morning (my time) @pauln

I checked for you this morning and if you do not want to change to a new VPS at this time, for what ever reason you might have, you can try the same method; but instead of overlay2 you can try aufs.

According to the Discourse launcher script:

  # 2. running an approved storage driver?
  if ! $docker_path info 2> /dev/null | egrep -q 'Storage Driver: (aufs|zfs|overlay2)$'; then

This means that, since some older versions of Debian support aufs and because Discourse appears to support aufs (from reading launcher); you can give that a try.

It’s really best to upgrade to a new Linux distro and kernel, since Debian 7.5 was EOL over two years ago, and it’s always best to get off EOL code when you can. I would go that route, for sure and move to the overlay2 storage driver (highly recommended). However, it is your choice and if you want to try aufs for fun, go for it. It’s always fun and rewarding to learn new things.

Reference:

Select a storage driver

HTH

---

Testbed Notes:

@pauln

To help you, I just took a fresh Linode Ubuntu VPS, installed Docker and changed the Storage Driver to aufs:

# docker info | grep aufs
 Storage Driver: aufs
  Root Dir: /var/lib/docker/aufs

Then I followed the standard Docker install directions:

https://github.com/discourse/discourse/blob/master/docs/INSTALL-cloud.md

and Discourse installed no problem on top of Docker with the aufs storage driver.

So maybe. you can try this on your Debian 7.5 VPS, for fun and knowledge, if you want.

Of course, recommended (officially and unofficially) is for you to move to a new supported VPS, as mentioned before. Please post back and update us on your decision and your progress.

[dillfrescott (Cross)]

Ho appena commentato il blocco di codice in launcher. a volte bisogna vivere pericolosamente !