boot2docker

问题 I am new to Docker and experimenting by creating an image from an existing Rails/Unicorn/MySQL app. My files are below and the image successfully creates but I'm unclear if things are actually working properly as I can't access the traditional Unicorn localhost URL, or the boot2docker IP. So my question is, how do I access a Unicorn server locally on OSX with a Docker image running? Dockerfile # Dockerfile FROM seapy/rails-nginx-unicorn # Publish port 8080 EXPOSE 8080 CMD ["bundle", "exec",

问题 Ok, I have exhausted pretty much all threads and articles, but still cant get my apache webserver to run in standalone mode on Centos Docker Container. Here is my simplified Dockerfile # install apache RUN yum -y install httpd # start the webserver ADD startservice /startservice RUN chmod 775 /startservice EXPOSE 80 CMD ["/startservice"] My starservice script just has #!/usr/bin/sh service httpd start I can build fine, but, cant seem to run the container in daemon/standalone mode. How do I do

问题 I have Docker Toolbox installed on windows 8.1 and I am creating an image based on ubuntu:latest (which should be 16.04). I want to make sure that my application is indeed run on 16.04. Here is my Dockerfile: FROM ubuntu:latest MAINTAINER xyz xyz@abc.com COPY apt.conf /etc/apt/ RUN apt-get -y update RUN apt-get -y install cmake RUN mkdir /usr/local/ COPY folder /usr/local/ RUN mkdir /usr/local/build CMD cd /usr/local/build CMD cmake /usr/local/ Once the image is built, i try to run : docker

问题 I'm trying to install a web application in a Docker container. I'm using OS X Yosemite version 10.10.1 I've been following the tutorial on Dockerizing a Node.js Web App here: https://docs.docker.com/examples/nodejs_web_app/ I downloaded and set up the boot2docker osx-installer at: github.com/boot2docker/osx-installer/releases/tag/v1.4.1 I entered these commands in the console in the following order: $ boot2docker init $ boot2docker start $ (boot2docker shellinit) Then I set the environmental

问题 I run a container and, say, install vim. I exit out of the container. I would then like to re-run the container and have still have vim installed. Is there a way to do this, because every time I restart a container vim is never there. 回答1: Is there a way to do this, because every time I restart a container vim is never there They are still there. when you run docker ps -a You should see all of them, some of them are not in running status, but in exited status. There are two ways to re-use the

问题 I recently installed boot2docker on my windows 7 64bit machine with all dependencies ( VirtualBox etc). However, when I executed it, it failed to start the docker server and preconfigured shell. From the cmd I could read the following exception: Failed to start machine "boot2docker-vm" 回答1: It turned out that the problem was the disabled virtualization . I found this by running VirtualBox and trying to manually boot the "boot2docker-vm" vitual machine. You can usually enable virtualization

问题 Followed a few tutorials online regarding installing boot2docker ISO release v1.3.0 on a windows 7 enterprise machine. The same steps work fine on a mac!!! We've a number of custom docker files that I want to link and manage for our development environment. However, when I run the boot2docker from the desktop it can take either 3 seconds or a minute to load, when it does the command line can lag about 20-30 seconds behind what the user is typing. I've tried reinstalling, cleaning anything

问题 I'm trying to set up a development environment for developing a play application in a docker container. I have created an image with sbt installed. I then map the project folder on my host to the container as a volume and run shell in interactive mode: docker run -v /Users/jorgen/dev/play-sbt-docker/app:/data/app -w /data/app -p 9999:9000 -i -t jorgenfb/sbt /bin/bash I then starts the play application by running sbt ~run . The play server starts just find, it even recompiles when i edit my

问题 I have been trying to connect to a docker container via ip, but reamins unsuccessful. When I used "docker inspect container-id" I get this result. My virtual box settings are by default: Can someone help me resolving this issue? 回答1: When running docker, you can specify which port(s) you'd like to be accessible to the outside world. Basic syntax is: docker run -p hostPort:containerPort imageName or just docker run -p hostPort imageName In the first case, externally, hostPort will be used, but

问题 So, despite Docker 1.3 now allowing easy access to external storage on OSX through boot2docker for files in /Users/, I still need to access files not in /Users/. I have a settings file in /etc/settings/ that I'd like my container to have access to. Also, the CMD in my container writes logs to /var/log in the container, which I'd rather have it write to /var/log on the host. I've been playing around with VOLUME and passing stuff in with -v at run, but I'm not getting anywhere. Googling hasn't