No container created during install

Product Support Self-hosting

AI-generated summary

No container created during install: bob1 is experiencing an issue with a Discourse installation on a fresh Ubuntu Server 18.04.4 LTS. The setup script fails to build the app and create a container, resulting in errors with docker, doctor, and launcher. Despite following the documented instructions and re-running the setup, the issue persists. Stephen suggests that the problem might be related to the server not running in true virtualization, as it’s hosted on a Synology NAS VM. bob1 confirms this and notes that the VM doesn’t appear to have VMX enabled, which he plans to investigate further with Synology support.

1

I followed the directions here: discourse/docs/INSTALL-cloud.md at main · discourse/discourse · GitHub

I am installing on a fresh install of Ubuntu Server 18.04.4 LTS, but after finishing the setup script, it dies claiming it failed to build the app and then that there is no container. doctor and launcher both fail with the same error.

docker: Failed to create the container ID file: open cids/app_bootstrap.cid: no such file or directory.

When I run docker --version it returns Docker version 18.09.9, build 1752eb3

I have delete /vars/discourse and recloned and ran it again twice with the same outcome.

Any ideas how to rectify this? Any more information I need to provide? I am not veering in any way from the documented instructions so I am not trying to do anything custom etc.

Thanks!

2

Where is this ubuntu server hosted? It sounds like it’s not running in true virtualization.

3

Good call! It is running in a VM on my Synology NAS and when I check /proc/cpuinfo, I don’t see it vmx enabled, I don’t see a way to enable it, but I’ll take that up with them!