Hi! I am currently trying to setup a discourse instance on CentOS 7 w/ OverlayFS… I seem to be getting this error when running discourse-setup, or manually trying to bootstrap with launcher. I, [2016-08-20T20:52:04.113288 #15] INFO -- : > cd /var/www/discourse && chown -R discourse /var/www/disco…

Most probably it’s because the backing xfs filesystem was not created with ftype=1 option. This is very common if you let the OS installer format the / fs and you just have /var/lib/docker on /. On newer docker verision (1.13?) with docker info you can see support d_type = false and that indicates …

That sounds right. And broken. We gave up on another hosting service because of some other strange problem. (I think it had to do with networking.) You might search for those terms with your hosting provider or docker and centos.

Not relevant in this case, self virtualized under ESXi. It’s a straight out of ISO install, with the exception of EPEL.

Trying with mainline kernel, will report back.

Same thing is occurring on mainline kernel, reverting to device mapper to see if outcome is successful… Definitely won’t be using that in production, however. Update: Works with devicemapper, must be a problem between overlay and discourse. I have tried with SELinux disabled, to no avail… as expec…

Devicemapper will corrupt your data over time in our experience, every time.

I have run overlay just fine in dev but not backed by xfs, only backed by ext4fs. It was certainly more quirky than running aufs, you got to be careful with inode counts.

I’ve heard that before (in regards to the inode counts). Device mapper is not something I will use in production. I’m not sure exactly how to track this down any further. I will attempt to use Fedora 24 and Overlay tomorrow, although I highly doubt it will help, seeing as I was using a newer kernel…

Hi everyone, I’m having the same problem here, trying to install discourse following the beginner install guide on an OpenStack CentOS 7 VM, getting exactly the same output & errors ( http://pastebin.com/PJBcSJcH ). This is my docker info: Containers: 0 Running: 0 Paused: 0 Stopped: 0 Images: 1 …

Any help or useful information about this problem would be greatly appreciated :slight_smile:

Docker file systems are, let’s say, complicated. We choose AUFS and we guarantee you can host your data there and everything will work out. We can’t afford to go after every distro+os fs+docker fs, so I can’t really help you on that.

Bootstrap fallisce su CentOS 7

Supporto Installazione

leoluk 5 Novembre 2017, 8:08pm 26

The issue described in this thread (permission denied) is due to SELinux, not ftype=0.

See Support official Docker packages on Red Hat/CentOS

Argomento		Risposte	Visualizzazioni
I can't start discourse on CentOS Self-hosting	7	2331	Maggio 12, 2017
Bootstrap fails on clean CentOS 7 install Self-hosting	6	4322	Giugno 8, 2024
Installation failing on CentOS 7.3 Support	10	3666	Settembre 5, 2022
Can't run ./launcher rebuild app - Docker storage driver is unsupported Support	72	12891	Settembre 25, 2019
Launching ./launcher bootstrap app returns Your Docker installation is not using a supported storage driver on CentOS 7 Self-hosting	16	2926	Giugno 16, 2019

Bootstrap fallisce su CentOS 7

Argomenti correlati