2014-07-21 482 views
3

虽然在Discourse的本地安装上运行我的./launcher bootstrap app命令/var/docker,但出现此错误。无法连接到github.com端口443:连接被拒绝,Bootstrap失败,Discourse 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而被拒绝。但是就在下载图像之前。所以我不明白。

## 
## 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;}' 

回答

2

你是在代理的背后吗?你有没有检查过你的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,应该“在”读。 正如我在发给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: '[email protected]'  # (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,神奇地解决了这个问题。但我不认为这是你的情况,我提到这一点以防万一......

+0

那么,它工作? – redlabo

+0

今晚我会放弃它,现在在工作。 – Jonathan

+0

码头DNS修复解决了我的问题。 – JBCP

相关问题