GoogleCodeExporter
commented
8 years ago Thanks for reporting this. We'll investigate.Original comment by z...@google.com on 4 Jan 2016 at 1:54
Open GoogleCodeExporter opened 8 years ago
GoogleCodeExporter
commented
8 years ago Thanks for reporting this. We'll investigate.Original comment by z...@google.com on 4 Jan 2016 at 1:54
GoogleCodeExporter
commented
8 years ago Let me know if you'd like the full log files, don't think they contain much
more than what I've already posted.Original comment by michael....@gmail.com on 4 Jan 2016 at 4:02
GoogleCodeExporter
commented
8 years ago Michael, are you the same person that reported the issue on Stack Overflow:
http://stackoverflow.com/questions/34423857/gae-managed-vm-deploy-gets-stuck-on-
docker-build ?
Either way, are you able to reproduce this consistently? If so, could you share
your Dockerfile? Feel free to email it to me directly at dlorenc@google.com
If you're able to SSH into the VM, the output of "cat /var/log/docker.log"
might be helpful.Original comment by dlor...@google.com on 5 Jan 2016 at 10:09
GoogleCodeExporter
commented
8 years ago I was the one who commented on the post, but I'm not the original poster.
I'll look into pulling those files.
Michael Sander
michael.sander@gmail.com
607-227-9859Original comment by michael....@gmail.com on 6 Jan 2016 at 2:33
GoogleCodeExporter
commented
8 years ago I've been having this issue too with my node app.
In my office, some people can deploy the app just fine and others are hitting
this bug, despite us all using the same version of gcloud SDK (91.0.1), the
same OS (OS X 10.11), same version of python (2.7.10 apple-compatible), etc.
I can provide some info that you asked for too, see below.
Dockerfile:
FROM node:4.2.3
RUN apt-get update -y && apt-get install -y -q --fix-missing \
graphicsmagick \
imagemagick
RUN mkdir -p /usr/src/app
WORKDIR /usr/src/app
COPY package.json /usr/src/app/
RUN npm --unsafe-perm install --production
COPY . /usr/src/app
CMD [ "npm", "start" ]
I SSHed into the VM and the output of /var/log/docker.log just repeats these
view messages (the first one a lot more frequently than the others):
time="2016-01-06T14:53:01.689552671Z" level=info msg="GET /version"
time="2016-01-06T14:53:04.881663725Z" level=info msg="GET /images/json"
time="2016-01-06T14:53:04.928656071Z" level=info msg="GET
/containers/json?all=1"Original comment by rich...@10kcoffees.com on 6 Jan 2016 at 4:18
GoogleCodeExporter
commented
8 years ago Hmm, one idea, Docker stores credentials in a file called ".dockercfg" if you
run "cat ~/.dockercfg", do you see any entries for "index.docker.io"?
Don't paste the contents of .dockercfg here, for registries other than GCR it
can contain private credentials.Original comment by dlor...@google.com on 6 Jan 2016 at 5:17
GoogleCodeExporter
commented
8 years ago Original comment by z...@google.com on 6 Jan 2016 at 5:30
GoogleCodeExporter
commented
8 years ago I don't have an entry there for "index.docker.io", though all the other entries
have the email set to "not@val.id" (I'm guessing they're examples).
I'm not sure if this is the cause though, as I can deploy other apps without
hitting this issue.Original comment by rich...@10kcoffees.com on 6 Jan 2016 at 5:46
GoogleCodeExporter
commented
8 years ago Same here. Below is the file with the auth sections redacted. I'm running on
windows btw, so I don't have a ~/.dockercfg. I snooped around and found it in
C:\home\Michael\.dockercfg, which is a bit of a weird place to put it.
{
"https://bucket.gcr.io": {
"email": "not@val.id",
"auth": "<REDACTED 1>"
},
"https://appengine.gcr.io": {
"email": "not@val.id",
"auth": "<REDACTED 1>"
},
"https://eu.gcr.io": {
"email": "not@val.id",
"auth": "<REDACTED 1>"
},
"https://gcr.io": {
"email": "not@val.id",
"auth": "<REDACTED 2>"
},
"https://us.gcr.io": {
"email": "not@val.id",
"auth": "<REDACTED 2>"
},
"https://asia.gcr.io": {
"email": "not@val.id",
"auth": "<REDACTED 1>"
},
"https://b.gcr.io": {
"email": "not@val.id",
"auth": "<REDACTED 1>"
}
}Original comment by michael....@gmail.com on 6 Jan 2016 at 6:40
Original issue reported on code.google.com by
michael....@gmail.comon 4 Jan 2016 at 8:57