docker容器的ERR_CONNECTION_REFUSED
我是新来的Docker,并试图做一个演示Rails应用程序。 我做了一个dockerfile,看起来像这样:
FROM ruby:2.2 # Install apt based dependencies required to run Rails as # well as RubyGems. As the Ruby image itself is based on a # Debian image, we use apt-get to install those. RUN apt-get update && apt-get install -y \ build-essential \ nodejs # Configure the main working directory. This is the base # directory used in any further RUN, COPY, and ENTRYPOINT # commands. RUN mkdir -p /app WORKDIR /app # Copy the Gemfile as well as the Gemfile.lock and install # the RubyGems. This is a separate step so the dependencies # will be cached unless changes to one of those two files # are made. COPY Gemfile Gemfile.lock ./ RUN gem install bundler && bundle install --jobs 20 --retry 5 # Copy the main application. COPY . ./ # Expose port 3000 to the Docker host, so we can access it # from the outside. EXPOSE 3000 # The main command to run when the container starts. Also # tell the Rails dev server to bind to all interfaces by # default. CMD ["bundle", "exec", "rails", "server", "-b", "0.0.0.0"]
我然后build立它(没有错误):
docker build -t demo .
然后运行它(也没有错误):
docker run -itP demo => Booting Puma => Rails 5.1.1 application starting in development on http://0.0.0.0:3000 => Run `rails server -h` for more startup options Puma starting in single mode... * Version 3.8.2 (ruby 2.2.7-p470), codename: Sassy Salamander * Min threads: 5, max threads: 5 * Environment: development * Listening on tcp://0.0.0.0:9292 Use Ctrl-C to stop
当我在一个单独的terminal上运行docker ps
命令来确定端口时,我得到:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 55e8224f7c15 demo "bundle exec rails..." About an hour ago Up About an hour 0.0.0.0:32772->3000/tcp ecstatic_bohr
但是,当我尝试使用Chrome或通过curl命令连接到http://localhost:32772
或http://192.168.99.100:32772
,我收到“连接被拒绝”。
当我通过bundle exec rails server
命令在我的本地计算机上的docker外运行应用程序时,它工作正常。 请注意,我在我的Win7机器上使用了Docker Toolbox
我可能做错了什么?
我花了几个小时,这个线程真的很有帮助。 我现在正在做的是通过虚拟机的IP地址访问这些服务。
你可以让你的虚拟地址运行:
docker-machine ls
然后尝试使用主机映射端口37772访问您的服务,如下所示:
http://<VM IP ADDRESS>:32772
希望这可以帮助。
上述技巧的结合起作用 –
我不得不使用http://<VM IP ADDRESS>:32772
(本地主机:32772没有工作),我不得不修复我的暴露端口匹配9292的TCP侦听端口。
我仍然不明白为什么TCP侦听端口默认为9292,而不是3000,但我会分开研究。
感谢您的帮助!