Why is every thread here closed? There are several relevant threads where I feel like it would make more sense to post my individual questions, but every old thread is closed (whether or not the problem was actually solved). Doesn’t this make it hard to identify when several people are having th…

[이미지] thornburg: The install directions are no good. I had to cobble together answers from multiple sets of directions to get it working. ALSO, why in the world would I ever run a remote script without seeing its contents? This is the worst installation method ever. Only one part has you …

The “upgrade docker manager” part (which I have to run first) just returns a bunch of lines which end (Operation not permitted). Here’s a snippet: $ cd /var/www/discourse/plugins/docker_manager && git fetch && git reset --hard HEAD@{upstream} error: unable to unlink old '.gitignore' (Operation not…

[이미지] trident: It looks like it works if you bootstrap while fully logged in as root; and not if you escalate via sudo. If you go the sudo route, it tries to create a key for the non-root user but never copies it over. @techapj can you repro this? If so we should fix the installer.

As a guess… What user is that being run as? The ./launcher ssh app should be dropping you in as root in the container. Also, that ssh key generation problem sounds like a bug with the launcher script – it should be using $HOME, but it is using /root. (or maybe a custom location, e.g. save to `./ss…

As a guess… What user is that being run as? The ./launcher ssh app should be dropping you in as root in the container. Also, that ssh key generation problem sounds like a bug with the launcher script – it should be using $HOME, but it is using /root. (or maybe a custom location, e.g. save to …

[이미지] codinghorror: can you repro this? If so we should fix the installer. Yeah there are no provisions for account elevation in launcher, I am pretty sure this would be happening. Fixing is tricky bash voodoo.

Does anyone have any additional advice that might help me solve this? I’m still unable to update.

Why not just run it under root?

[이미지] sam: Why not just run it under root? Run what under root? I can’t SSH into the box, and the GUI upgrade doesn’t give me any option to change the way it runs. Are you suggesting I reinstall using root instead of sudo? Requiring root is a horrible security practice. I’m not sure that …

Within the context of an already isolated VM or LXC container, it can make sense. And since our only recommended and supported install is Docker…

Install issues when not root

Product Support Self-hosting

codinghorror (Jeff Atwood) 6월 14, 2014, 3:28오후 4

@techapj can you repro this? If so we should fix the installer.

글		댓글	조회수
Cannot connect to docker daemon Self-hosting docker	9	1144	3월 7, 2023
Failed to install Discourse in Ubuntu14.04: docker problems Self-hosting docker	19	8620	1월 25, 2015
Discourse in a Docker container Self-hosting hosting	27	13075	2월 3, 2014
I can't follow the …/admin/upgrade instruction Product Support	1	514	4월 12, 2019
Failed web upgrade Self-hosting	18	1386	12월 1, 2022

Install issues when not root

Related topics