Stop and remove docker container by mistake

Product Support Self-hosting

AI-generated summary

Eduar_Ramos accidentally stopped and removed their Discourse Docker container and encountered an error about an unsupported storage driver when trying to restart it. The error suggested using aufs, though overlay2 (which they are using) is also acceptable. sam recommended running git pull && ./launcher rebuild app to recover, noting that rebuilding won’t delete data since it’s stored outside containers as confirmed by jomaxro. Eduar_Ramos shared their docker info, showing they’re on overlay2 with Ubuntu 18.04. Despite rebuilding, the service still wouldn’t start properly, and they shared a screenshot showing the container running but not accessible post 6. Falco pointed out that installing Discourse alongside Plesk (visible in their setup) is unsupported and advised following the official standard installation guide. The core issue appears to be a misconfiguration or conflict due to the unsupported environment rather than data loss or driver incompatibility.

1

Hello everyone, by mistake I gave stop and remove to the docker container of discourse and when trying to launch again, when trying / launcher start I get the following error:
"Your Docker installation is not using a supported storage driver. If we were to proceed you may have a broken install.
aufs is the recommended storage driver, although zfs / btrfs / overlay and overlay2 may work as well.
Other storage drivers are known to be problematic.
You can tell what filesystem you are using by running “docker info” and looking at the ‘Storage Driver’ line.

If you wish to continue anyway using your existing unsupported storage driver,
read the source code of launcher and figure out how to bypass this check."

What should I do to recover my site?

2

I recommend you re-install docker with a supported driver. What is the output of docker info

At a minimum to get back running git pull && ./launcher rebuild app should get you back and running as long as your using one of the supported engines.

3

Thanks for the reply.

In a few hours I post the output of docker info.

If I rebuild does it mean I lose the data?

4

No, the database and other content is stored outside docker containers. Containers can be safely rebuilt at any time (though it will cause brief downtime for your site if running).

5

Docker info:

Client:
 Debug Mode: false

Server:
 Containers: 11
  Running: 5
  Paused: 0
  Stopped: 6
 Images: 18
 Server Version: 19.03.5
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Native Overlay Diff: true
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: b34a5c8af56e510852c35414db4c1f4fa6172339
 runc version: 3e425f80a8c931f88e6d94a8c831b9d5aa481657
 init version: fec3683
 Security Options:
  apparmor
  seccomp
   Profile: default
 Kernel Version: 4.15.0-76-generic
 Operating System: Ubuntu 18.04.3 LTS
 OSType: linux
 Architecture: x86_64
 CPUs: 4
 Total Memory: 7.789GiB
 Name: plesk-s-1vcpu-2gb-ams3-01.local
 ID: UNYW:S4UK:I7CE:IVI4:ZR6I:AXPR:3LTL:3OTF:4VD4:GEFM:VVP6:3WZ5
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false
6

Hi Sam, try this, but I cannot upload the service again, the base image does not run again, I am attaching plesk image and the docker ps command:

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
aa5a18a5467b 0c04b35ef09a "/ sbin / boot" 9 days ago Up 2 minutes 0.0.0.0:8070->80/tcp, 0.0.0.0:9443->443/tcp app

imagen
imagen1920×1040 80.7 KB

Thanks for the help.

7

Installing alongside plesk or any similar software is not supported.

Please follow the Discourse official Standard Installation