docker-machine

问题 I´m using docker tools on windows. create command was working perfectly last week and I managed to create a number of machines on Digital Ocean. Then I tried today with no success. I repeated the same command with different regions and I always get the same result: λ docker-machine create -d digitalocean --digitalocean-access-token=MYTOKEN --digitalocean-region=ams2 vmname Running pre-create checks... Creating machine... (fernu) Creating SSH key... (fernu) Creating Digital Ocean droplet...

问题 I'm using https://github.com/sameersbn/docker-mysql to run a mysql container using docker-machine in OSX with virtualbox. I created a new machine docker-machine create --driver virtualbox mytest The IP is docker-machine ip mytest 192.168.99.103 I run the container like this: docker run -p 3306:3306 --name mysql -d \ -v /opt/mysql/data:/var/lib/mysql \ -e 'DB_USER=sampleuser' -e 'DB_PASS=samplepass' -e 'DB_NAME=sampledb' -e 'DB_REMOTE_ROOT_NAME=root' -e 'DB_REMOTE_ROOT_PASS=samplerootpass' \

问题 So I have a simple containerised django project, with another container for sass css compilation. I use docker-compose with a docker-machine, but when I fire it up, the web container doesn't have any of my local files (manage.py etc) in, so it dies with a file not found: manage.py error. Let me explain more: docker-compose.yml web: build: . volumes: - .:/app ports: - "8001:5000" sass: image: ubuntudesign/sass command: sass --debug-info --watch /app/static/css -E "UTF-8" volumes: - .:/app

问题 I'm facing this weird problem , struggling to solve since almost couple of days. Working: On mac mini command prompt , I switch to jenkins user and can run docker command without any problem. Not Working: but when I run a jenkins job , inside shell command step docker is not recognized. I'm getting error docker: command not found docker --version But mentioning explicit path of docker , does work /Users/buildserver/Library/Group\ Containers/group.com.docker/bin/docker --version Question : Why

问题 Everytime I try to create a new instance via docker-machine on open stack, I always get this error for validating the certs. I have to end up regenerating the certs right after I create the instance for me to be able to use the instances. $ docker-machine create --driver openstack --openstack-ssh-user root --openstack-keypair-name "KeyName" --openstack-private-key-file ~/.ssh/id_rsa --openstack-flavor-id 50 --openstack-image-name "Ubuntu-16.04" manager1 Running pre-create checks... Creating

问题 I have the following in my docker file: RUN sudo apt-get install sshpass -y RUN sshpass -p userPassword scp -r user@server:~/data/* ./ But when I try and build my image it fails with: Exception caught: The command '/bin/sh -c sshpass -p userPassword scp -r user@server:~/data/* ./' returned a non-zero code: 6 -> [Help 1] However, if I remove these lines, build the image, ssh onto the container and manually run the command from bash it works perfectly. Can anyone tell me how to get around this?

问题 Before asking this question I have read quiet of articles and stackoverflow questions but I couldn't get the right answer for my setup(perhaps it is already answered). Here is the architecture I have been struggling to get it to work. I have three physical machines and I would like to setup the Docker swarm with multi-host networking so that I can run docker-compose. For example: Machine 1(Docker Swarm Manager and Contains Consoul)(192.168.5.11) Machine 2(Docker Swarm Node)(192.168.5.12)

问题 I need to give an argument while running Docker Image which will be a number from 0-3. Dockerfile has the following: WORKDIR "mydir/build" CMD ./maker oneapp > /artifacts/oneapp_$1.log ; ./maker twoapp > /artifacts/twoapp_$1.log ; ./maker -j13 threeapp > /artifacts/threeapp_$1.log I will be running the same Docker Image multiple times so I need logs to be saved in /artifacts appended with _0, _1, _2, _3, as appropriate. I tried keeping this in Docker file but don't want to pass this full line

问题 Docker seems to be creating a bridge after a container starts running that then conflicts with my host network. This is not the default bridge docker0, but rather another bridge that is created after a container has started. I am able to configure the default bridge according to the older user guide link https://docs.docker.com/v17.09/engine/userguide/networking/default_network/custom-docker0/, however, I do not know how to configure this other bridge so it does not conflict with 172.17. This

问题 I'm running Docker 1.9.1 on OSX, and I'm connected to my private work network with Cisco AnyConnect VPN. A service that I'm running in a Docker container connects to a DB within the work network, and is unreachable from within the container, but reachable from outside the container in OSX. It's also reachable from within the container if I'm connected directly to the work network, not through VPN. I suspect I may have to do some network configuration with the docker-machine VM, but I'm not