Struggling with Docker, is there another way?
I have been trying on and off for the last week or so to install Loomio using the docker method, I've put in quite a few hours, and I am finding it frustrating.
I'm an experienced developer and web server admin but I have never used Docker before. When things go wrong I usually know how to start debugging them, but with Docker there is a whole layer in between which I don't understand, and I find it quite hard to accept that I will have to learn about it just to install Loomio. I know it's a useful thing to learn, but I was hoping to get Loomio up and running quickly so as to start using it! A whole array of docker containers linked together is no mean feat to understand.
I get the impression that @robertguthrie is the only person who knows the loomio docker system inside out and is therefore swamped with requests for help, but that you are a busy chap, like the rest of us, and cannot be expected to be there at the beck and call of anyone who attempts installation.
If there was a way of installing it that did not require this extra layer, perhaps people would be able to help each other more, and get help from Stack Overflow and the like.
It's also difficult to make configuration changes - I tried to run it on a different port, but failed. Which means I have to use a whole VPS for this, rather than running it on the same server as another bunch of websites. In fact being forced to use nginx makes this difficult anyway; I have a bunch of apache vhosts and was hoping this would just be another one.
Also, the docker container uses a lot of RAM, which is what drives up the cost of a VPS. So it is costing a lot to run this.
I'm sorry, I realise this probably comes across as a rant, but I think it is important for free software projects to be relatively easy to install, and not to rely on one beleagured person as the font of all knowledge ...
Robert Guthrie Wed 22 May 2019 8:36PM
Boarding a plane. I'll check back later today
Brendan Butler Wed 22 May 2019 8:37PM
Port 80 and 443 are both open; using a Google VPS and I had selected both to be open when creating it. DNS is also set up (other than MX, I was going to set that up when I had it all working; is that maybe the problem?)
Safe travels!!!
Brendan Butler Wed 22 May 2019 9:00PM
Alright, still getting the 503 error and checked the logs and saw a bunch of various errors. Most are regarding the let's encrypt, but I saw some that weren't related. I am on the way home now, once I get home I will try copy pasting the entire error log into a Pastebin
Brendan Butler Wed 22 May 2019 10:03PM
Got home. The logs are VERY large,
I am unsure what in here is relating to my problem; though I am assuming its not all those letsencrypt errors as that would only deal with the SSL (I should still be able to connect to http, where Chrome would mention its insecure).
The weird part I find is that LetsEncrypt did seem to work; the page has the secure lock and it says valid from today on:
Klaus Kobald Wed 22 May 2019 10:50PM
YES!
And it helps watching the log, because it takes some while for building!
So I´m getting the login page and will continue tomorrow! Greetings from Austria! :clap:
Robert Guthrie Wed 22 May 2019 11:38PM
restarting with docker-compose down; docker-compose up -d can sort out let's encrypt issues sometimes. Also docker-compose logs letsencrypt will show just logs from that container.
Brendan Butler Thu 23 May 2019 1:30AM
Restarting the docker-compose seemed to fix the letsencrypt; and it all got up with no errors. I have been watching the logs and I am seeing no errors, but it's been roughly 2 hours and I am getting 503 when trying to connect.
loomio-worker | [Worker(host:4c6775a2dec8 pid:7)] 6 jobs processed at 0.0526 j/s, 0 failed
loomio-worker | 2019-05-23T01:11:32+0000: [Worker(host:4c6775a2dec8 pid:7)] 6 jobs processed at 0.0526 j/s, 0 failed
loomio-nginx | nginx.1 | 2019/05/23 01:28:50 [error] 84#84: *20 connect() failed (111: Connection refused) while connecting to upstream, client: 72.137.176.178, server: test......xyz, request: "GET / HTTP/2.0", upstream: "http://172.17.0.5
:3000/", host: "test......xyz"
loomio-nginx | nginx.1 | test.....xyz 72.137.176.178 - - [23/May/2019:01:28:50 +0000] "GET / HTTP/2.0" 502 575 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3729.157 Safari/537.36"
loomio-nginx | nginx.1 | test......xyz 72.137.176.178 - - [23/May/2019:01:28:50 +0000] "GET /favicon.ico HTTP/2.0" 502 575 "https://test.....xyz/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/
74.0.3729.157 Safari/537.36"
loomio-nginx | nginx.1 | 2019/05/23 01:28:50 [warn] 84#84: *20 upstream server temporarily disabled while connecting to upstream, client: 72.137.176.178, server: test....xyz, request: "GET / HTTP/2.0", upstream: "http://172.17.0.5:3000/"
, host: "test......xyz"
Robert Guthrie Thu 23 May 2019 8:48AM
It would be a good idea to run docker-compose logs app to see just the rails logs - that's likely where the issue is.
Brendan Butler Thu 23 May 2019 11:00AM
After waking up and checking the website (I left the serverto do it's thing) I found this:https://i.godhub.xyz/05-23-2019-rLNLLRwiv1.png
Maybe this has to do with my cpu, it was near its limit when I started to install this. Maybe when I get my new server into my datacenter in the up coming days I can try again on a more powerful machine.
Robert Guthrie · Wed 22 May 2019 8:35PM
Also you need to be sure that port 80 is open and your dns is correct for letsencrypt.