Question

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

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"

如果您没有添加DNS（可以使用nslookup找到），则可能无法解析GitHub的名称。但是，由于您尝试连接并未明确返回未解决的名称，因此我不认为您在此担心。但奇怪的是，我必须这样做才能让它发挥作用。对于其他人，我已经提到了在GitHub上填写的问题中该怎么做： https://github.com/discourse/discourse_docker/issues/79

修改我纠正了这一点，没有ln，它应该在＆＃39;中读到。正如我在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在其配置文件中配置了很多东西。但令我惊讶的是，代理配置似乎从未被考虑过。但是，dns部分很有趣，因为我得到了名称解析错误，尽管已经配置了公共DNS。所以我添加了我公司的dns，神奇地解决了这个问题。但我不认为这是你的情况，我提到这是为了以防万一......

Answer 2

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

无法连接到github.com端口443：连接被拒绝，无法启动，话语Docker

2 个答案: