Question: docker-machine is setting up ssl certs, what for? for communication among the other docker hosts?

Asked By
Asked At
2017-09-26 06:00:54

Found 15 possible answers.

User Answered At Possible Answer
dudhat 2017-09-26 07:32:54 i am try to create docker image of angular 2 application ? any one can help me with this what is the problem at process._tickCallback (internal/process/next_tick.js:103:7) at check_port_1.checkPort.then.port (/node_modules/@angular/cli/commands/serve.js:121:26) at (/node_modules/@angular/cli/tasks/serve.js:51:63) TypeError: Cannot read property 'config' of null Cannot read property 'config' of null but when i am try to run it i am getting error like i am able to build image successfully CMD ["npm", "start"] EXPOSE 4200 COPY angular-cli.json angular-cli.json COPY angular-cli.json ./.angular-cli.json COPY . . CMD npm install COPY package.json . FROM node:6.9.2
ulan 2017-09-26 08:50:36 looks like a non docker related error. how do you start the app locally without docker? also a tip, CMD npm install would be better to use RUN instead so RUN npm install
shanmugam07 2017-09-26 09:05:12 @dudhat Yup. Does the application works locally ?
dudhat 2017-09-26 09:06:23 @shan yes application work perfectly in locally thanks for reply
shanmugam07 2017-09-26 09:20:03 looks like it’s
twinkle1chawla 2017-09-26 10:36:30 Is there any way I can link my private docker registry to google container registry? So that google container registry can automatically fetch newer images from my local registry or local registry can push images to google registry!
jhuizy 2017-09-26 12:40:22 docker push ?
pizza 2017-09-27 16:18:12 Hey friends, I’m struggling a bit with a docker cacheing issue. Does anyone see any issues with my logic above? What happens instead, is that the whole cache busts, and I get the message: Status: Downloaded newer image for erlang:20.0.4 , even though they are both literally crated from the same docker file. I have an idempotent build environment, so when the next build starts, I pull the docker image mydockerimage:lockfile_hash , then kick off the build in the hope that my docker build will use the mydocekrfile:lockfile_hash layers to skip most of the build time. So, I’m trying to speed up my image builds through some clever cacheing. I figured out that we can cut down our compile / linting time tremendously by doing a hash on our lock file. So my solution is to after each build, I hash the lockfile, and push the docker image I just built with that lockfile as the tag.
roth 2017-09-27 17:10:58 @pizza What's your FROM on each of the Dockerfiles? If you're trying to build based on that base image you need to be calling FROM mydockerimage:lockfile_hash
pizza 2017-09-27 17:19:47 @roth they’re both from erlang:20.0.4 , and I was HOPING that being FROM the same image would mean that Docker would be smart and have them re-use layers. Is this not the case?
peterr 2017-09-27 17:21:30 the two builds are occurring on different docker daemons?
yarmiganosca 2017-09-27 17:22:29 @pizza if the layers are identical, and you haven't blown your cache already on that build, then yes they will be reused across Dockerfiles
pizza 2017-09-27 17:23:07 @peterr yeah, they are I pull the “cache” image form a docker repo
roth 2017-09-27 17:24:04 does that image show up when you run docker images ?
yarmiganosca 2017-09-27 17:24:55 @pizza let's call it a "stage" or "temp" image given that we're also discussing the behavior of the docker layer cached, just to cut down on confusion

Related Questions