boot2docker

Application server in Docker - war deployment with IntelliJ

前提是你 提交于 2019-12-01 01:07:06
Hello dear programmers, I'm looking into setting up my development with docker containers since I'm currently working on windows, my setup is now as follows: A docker image including a jboss which is started and already running An hg repo checked out on my windows file system which is imported into IntelliJ A shared folder which is mapped to the deploymentfolder in the docker image Whenever I want to deploy my war, I'll let IntelliJ build the artifact as an exploded war with output directory to $THE_SHARED_FODLER/mywar.war. Then I'll touch a file in the same repo with mywar.war.deploy. Since

Application server in Docker - war deployment with IntelliJ

三世轮回 提交于 2019-11-30 20:48:16
问题 Hello dear programmers, I'm looking into setting up my development with docker containers since I'm currently working on windows, my setup is now as follows: A docker image including a jboss which is started and already running An hg repo checked out on my windows file system which is imported into IntelliJ A shared folder which is mapped to the deploymentfolder in the docker image Whenever I want to deploy my war, I'll let IntelliJ build the artifact as an exploded war with output directory

boot2docker, docker, django on mac os x

☆樱花仙子☆ 提交于 2019-11-30 16:04:28
问题 I want to run a Django app in docker on Mac OS X. I have installed docker using the get-started tutorial. I refer to the Django doc in docker-library to build image, https://github.com/docker-library/docs/tree/master/django, I add the Dockerfile in a new Django project folder The problem is I build the image and run the container successfully but whenever I visit container-ip:8000 or http://localhost:8000 , it doesn't work. Anyone have solutions? Here are the images and container info; docker

Docker complains about invalid certificate after update to v1.7.0

倖福魔咒の 提交于 2019-11-30 11:19:54
问题 After updating to Docker v1.7.0 (and also boot2docker), I'm getting the following error when running docker ps : x509: certificate is valid for 127.0.0.1, 10.0.2.15, not 192.168.59.103 Is this a known issue with this version, and what can I do to fix this? 回答1: This is a known issue introduced in version 1.7.0 of boot2docker: https://github.com/boot2docker/boot2docker/issues/824 Update to boot2docker 1.7.1 Updating to boot2docker 1.7.1 fixes this issue, as described here. Options for

dockerd vs docker-containerd vs docker-runc vs docker-containerd-ctr vs docker-containerd-shim

元气小坏坏 提交于 2019-11-30 10:27:16
问题 This stuff is really getting confused now. Can someone please explain what's going on. Just the straight one liner difference. dockerd libcontainerd containerd docker-containerd docker-runc docker-containerd-ctr docker-containerd-shim thanks 回答1: dockerd - The Docker daemon itself. The highest level component in your list and also the only 'Docker' product listed. Provides all the nice UX features of Docker. (docker-)containerd - Also a daemon, listening on a Unix socket, exposes gRPC

Enabling Remote API in Docker on Mac OS X (boot2docker)

故事扮演 提交于 2019-11-30 09:39:40
I can't seem to figure out how to enable the remote API when using boot2docker. I am trying to use dockerode as follows: Docker = require('dockerode') docker = new Docker(socketPath: "/var/run/docker.sock") container = docker.getContainer('<my_container_id>') container.inspect (err, data) -> debug data Data is null, despite there being a container with the id ''. I suspect this is because there is no /var/run/docker.sock on the OS X host, and that I would need to use something like: var docker2 = new Docker({host: 'http://192.168.1.10', port: 3000}); ... but can't figure out how to configure

Move boot2docker and .docker folder in other drive

被刻印的时光 ゝ 提交于 2019-11-30 04:47:22
I'm new in docker. I have installed docker in windows in the D drive but the Boot2docker VM is in the user folder in the C drive. I dont have enough space in the C and the boot2docker is growing when i pull softwares from the docker hub. So I want to move the boot2docker or the .docker folder in the D drive. Is it possible ? and how can i do ? Larry Cai Moving existing disk The big size for the VM machine is .vmdk or .vdi , so you just need to move the disk to Drive D instead of moving whole .docker directory. What you can do in simple way in Oracle VirtualBox Manager GUI: Stop the boot2docker

OSX boot2docker hangs on “Waiting for VM and Docker daemon to start …”

纵饮孤独 提交于 2019-11-30 03:04:08
I've installed boot2docker on OSX 10.8.5 and it seems that the installation went fine, but when I try to launch boot2docker I get the following, which hangs indefinitely: $ /usr/local/bin/boot2docker up Waiting for VM and Docker daemon to start... ..........................................................................oooooooooooooooooooooooooooooo What steps should I take to debug this? I haven't been able to find any information on this particular issue. $ boot2docker version Boot2Docker-cli version: v1.4.1 Git commit: 43241cb $ docker version Client version: 1.4.1 Client API version: 1.16

How to copy file from host to container using Dockerfile

别等时光非礼了梦想. 提交于 2019-11-30 01:09:56
I have written a Dockerfile which looks like this FROM ubuntu:12.04 RUN apt-get update RUN apt-get install -y wget Now I'm having a file called abc.txt in my host machine. How can I copy it to this container. Is there any step that I can add in Dockerfile which copy from Host to Container. george.yord Use COPY command like this: COPY foo.txt /data/foo.txt # where foo.txt is the relative path on host # and /data/foo.txt is the absolute path in the image read more details for COPY in the official documentation An alternative would be to use ADD but this is not the best practise if you dont want

Docker mongo image 'Connection refused' from other container

走远了吗. 提交于 2019-11-30 00:27:03
I'm new to docker. I'm trying to create a MongoDB container and a NodeJS container. My file looks: version: '2' services: backend: image: node:5.11-onbuild ports: - "3001:3001" volumes: - .:/code working_dir: "/code" links: - mongodb mongodb: image: mongo:3.3 expose: - 27017 It should run npm install and then node . . But docker-compose up ends up with [MongoError: connect ECONNREFUSED 127.0.0.1:27017] while the command node . . I think this is because of the bind_ip = 127.0.0.1 in the file /etc/mongod.conf . Is this right? I use boot2docker on a Win10 system. How can I solve this problem so