无法连接到github.com端口443:连接被拒绝，启动失败，讨论Docker

Question

当我在本地安装的Discourse上从/var/docker运行我的./launcher bootstrap app命令时，我得到这个错误。

fatal: unable to access 'https://github.com/SamSaffron/pups.git/': Failed to connect to github.com port 443: Connection refused
FAILED TO BOOTSTRAP

以下是我的containers/app.yml的内容。我一直在使用this指南来尝试让它启动并运行起来。我听说有些人因为iptables -L包含一些连接到互联网的rules blocking the docker container而导致HTTP连接被拒绝的问题。但它只是在下载图像之前的片刻。所以我不明白。

##
## After making changes to this file, you MUST rebuild for any changes
## to take effect in your live Discourse instance:
## 
## /var/docker/launcher rebuild app
##

## this is the all-in-one, standalone Discourse Docker container template
templates:
  - "templates/cron.template.yml"
  - "templates/postgres.template.yml"
  - "templates/redis.template.yml"
  - "templates/sshd.template.yml"
  - "templates/web.template.yml"

## which TCP/IP ports should this container expose?
expose:
  - "127.0.0.1:20080:80"   # fwd host port 80   to container port 80 (http)
  - "2222:22" # fwd host port 2222 to container port 22 (ssh)

params:
  ## Which Git revision should this container use?
  version: HEAD

env:
  ## How many concurrent web requests are supported?
  ## With 2GB we recommend 3-4 workers, with 1GB only 2
  # UNICORN_WORKERS: 3
  ##
  ## List of comma delimited emails that will be made admin on signup
  DISCOURSE_DEVELOPER_EMAILS: <%= ENV['EMAIL_ADDRESS'] %>
  ##
  ## The domain name this Discourse instance will respond to
  DISCOURSE_HOSTNAME: 'localhost'
  ##
  ## The mailserver this Discourse instance will use
  DISCOURSE_SMTP_ADDRESS: smtp.gmail.com
  DISCOURSE_SMTP_PORT: 465
  DISCOURSE_SMTP_USER_NAME: <%= ENV['GMAIL_USERNAME'] %>
  DISCOURSE_SMTP_PASSWORD: <%= ENV['GMAIL_PASSWORD'] %>
  ##
  ## the origin pull CDN address for this Discourse instance
  # DISCOURSE_CDN_URL: //discourse-cdn.example.com

## These containers are stateless, all data is stored in /shared
volumes:
  - volume:
      host: /var/docker/shared/standalone
      guest: /shared

## The docker manager plugin allows you to one-click upgrade Discouse
## http://discourse.example.com/admin/docker
hooks:
  after_code:
    - exec:
        cd: $home/plugins
        cmd:
          - git clone https://github.com/discourse/docker_manager.git

## Remember, this is YAML syntax - you can only have one block with a name
run:
  - exec: echo "Beginning of custom commands"

  ## If you want to configure password login for root, uncomment and change:
  #- exec: apt-get -y install whois # for mkpasswd
  ## Use only one of the following lines:
  #- exec: /usr/sbin/usermod -p 'PASSWORD_HASH' root
  #- exec: /usr/sbin/usermod -p "$(mkpasswd -m sha-256 'RAW_PASSWORD')" root

  ## If you want to authorized additional users, uncomment and change:
  #- exec: ssh-import-id username
  #- exec: ssh-import-id anotherusername

  - exec: echo "End of custom commands"
  - exec: awk -F\# '{print $1;}' ~/.ssh/authorized_keys | awk 'BEGIN { print "Authorized SSH keys for this container:"; } NF>=2 {print $NF;}'

Answer 1

你在代理背后吗？您检查过DNS设置了吗？为了让它在/etc/default/docker中运行，我必须这样做

DOCKER_OPTS="--dns 8.8.8.8 --dns 8.8.4.4 --dns x.x.x.x"

如果你不添加你的GitHub (你可以用nslookup找到它)，很可能你不能解析DNS的名字。但是，由于您尝试连接时不会显式返回未解析的名称，因此我不认为您在这里会受到影响。但奇怪的是，我必须这样做才能让它工作。对于其余部分，我已经提到了在GitHub上填充的问题中应该做些什么：https://github.com/discourse/discourse_docker/issues/79

编辑：我更正了这一点，没有ln，应该是'in‘。正如我在给GitHub的问题中所说的，在代码中缺乏对代理的考虑。但是你有代理服务器或者直接访问网络吗？我打赌你有代理律师。如果是，请在我提供的链接中使用我的解决方案。基本上，如果不将HTTP_PROXY添加到话语图像的环境变量中，依赖于它的任何命令都不会起作用(就像gem命令的情况一样)。

示例：

DISCOURSE_SMTP_ADDRESS: smtp.mandrillapp.com                # (mandatory)
HTTP_PROXY: http://x.x.x.x:3128/ # my add
DISCOURSE_SMTP_PORT: 587                        # (optional)
DISCOURSE_SMTP_USER_NAME: 'xx@xx.com'      # (optional)
DISCOURSE_SMTP_PASSWORD: Password               # (optional)

此外，git有自己的指定代理的方式，所以我将其添加到脚本中以使其运行。否则，git将被卡住，当它试图从存储库中拉出时，将发生超时(似乎是您的情况)。

替换话语的启动器脚本：

run_command="$run_command git pull &&"

至

run_command="$run_command git config --global http.proxy http://x.x.x.x:3128/ && git pull &&"

和/或(应该也可以，事实上，如果我没记错的话，我必须同时做这两件事…)

/bin/bash -c "$run_command") \

至

/bin/bash -c "git config --global http.proxy http://x.x.x.x:3128/;$run_command") \

更清楚了？关于dns，docker在它的配置文件中配置了很多东西。但令我惊讶的是，代理配置似乎从未被纳入account.Yet，dns部分很有趣，因为我也收到了名称解析错误，尽管公共dns已经配置。所以我添加了我公司的dns，它神奇地解决了这个问题。但我不认为这是你的情况，我提到这是为了以防万一...

Answer 2

在重试之前尝试add your SSH key to Github