From 93cbc0d483e9cdd811ece0f04eb8afad74669ef8 Mon Sep 17 00:00:00 2001 From: Michael Brown Date: Sun, 3 Aug 2014 00:32:19 -0400 Subject: [PATCH] Add more suggestions for troubleshooting. --- README.md | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index fdf06c4..c425c0a 100644 --- a/README.md +++ b/README.md @@ -150,14 +150,19 @@ For a Discourse instance to function properly Email must be set up. Use the `SMT ### Troubleshooting +View the container logs: `./launcher logs my_container` + You can ssh into your container using `./launcher ssh my_container`, we will automatically set up ssh access during bootstrap. -You can spawn a shell inside your container using `./launcher enter my_container`. This is the most foolproof method if you have local root access. +Spawn a shell inside your container using `./launcher enter my_container`. This is the most foolproof method if you have host root access. + +You got network errors trying to retrieve code from `github.com` or `rubygems.org`? Try again - sometimes there are temporary interruptions and a retry is all it takes. Behind a proxy network with no direct access to the Internet? Add proxy information to the container environment by adding to the existing `env` block in the `container.yml` file: + ```yaml env: - …existing info… + …existing entries… HTTP_PROXY: http://proxyserver:port/ http_proxy: http://proxyserver:port/ HTTPS_PROXY: http://proxyserver:port/ -- 2.25.1