@nl5887 commented on GitHub:
Don't expect that to solve this issue. But lets see first how it works without docker (they are running just one docker container per vm), so the docker container…
@nl5887 commented on GitHub:
Thanks for noticing. Docker and Elastic Beanstalk failed recovering from the docker process crashing. I've restarted everything and will remove the docker layer.
@songgao commented on GitHub:
Thanks @nl5887 for the fast response! I'm gonna close the issue then.
Have you considered CoreOS? :)
@robertgendler commented on GitHub:
The script has been removed in our current release. So this has been resolved.
@songgao commented on GitHub:
Got you. Was it docker itself, or the transfersh-server process within the container that crashed? I mentioned CoreOS mainly because of the rkt runtime. It has a…
@dschep commented on GitHub:
@nl5887 is https://transfer.sh down again?
$ curl -I https://transfer.sh
HTTP/1.1 503 Service Unavailable: Back-end server is at capacity
Connection:…
@g33k247 commented on GitHub:
curl -I https://transfer.sh curl: (7) Failed to connect to transfer.sh port 443: Connection refused
@sophuric commented on GitHub:
@nl5887 is https://transfer.sh down again?
$ curl -I https://transfer.sh HTTP/1.1 503 Service Unavailable: Back-end server is at capacity …
@golbiga commented on GitHub:
Configuration profile will re-apply settings, keeping as is.