Hello;
I’m trying to setup on a virtual server with Plesk Panel installed. Could you help?
./discourse-setup
Failed to find docker or docker.io on your PATH.
Enter to install Docker from https://get.docker.com/ or Ctrl+C to exit
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 20009 100 20009 0 0 219k 0 --:--:-- --:--:-- --:--:-- 219k
# Executing docker install script, commit: b2e29ef7a9a89840d2333637f7d1900a83e7153f
+ sh -c apt-get update -qq >/dev/null
W: GPG error: https://repo.cloudlinux.com/kernelcare-debian/8 stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 6DC3D600CDEF74BB
E: The repository 'https://repo.cloudlinux.com/kernelcare-debian/8 stable InRelease' is not signed.
Still failed to find docker or docker.io on your PATH.
Docker install failed. Quitting.
Not much. That’s a very non-standard configuration. You definitely can’t use discourse-setup. And and discourse-setup suggests, you’ll need to install Docker. If you want to install Discourse in plesk, and you didn’t get as far as installing docker, then I think it’ll take you a while.
I’d recommend that you first install Discourse on its own VM to see how it works the easy and supported way, and then, if you want to try to get Discourse to co-exist with Plesk for some reason, you can go about seeing how to change it so that it might co-exist with Plesk. There are topics about running Discourse with other web servers, so they’ll offer some help, but I’m not aware of any that work with Plesk. I have one client whose VM has plesk and we disabled Plesk and let Discourse have all the ports, but every now and again something would happen and Plesk would take over the ports again and stop Discourse from working.