Hi again Matt,
Thank you for being so thorough and looking into all the separate steps
like that.
At this point, I think this will require some backend investigation on our
part to figure out where this is holding up.
Do you mind posting the most basic "helloworld" example (or something
equal
Actually I don't think this will work as they are private images, and I get an
error that the base image isn't found.
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an
I'm not using the "--docker-build" flag at all. I will try
--docker-build=local and report back. Thanks,
matt
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an emai
Hey Matt,
I looked a little bit further into your error and I have a question. Are
you using the "--docker-build=remote" flag in your build (or simply not
using the "--docker-build", as this is the default behavior)? It is
possible this is the issue you're currently facing here is that the remo
Ok, I tried with our basic Docker image, and that uploaded fine
(snhq/basic-gae). So it looks like it's something with this Dockerfile that
is causing the problem:
#
FROM snhq/basic-gae
RUN apt-get update
# install numpy/scipy
RUN apt-get install -y libatla
I tried it with 50GB, although my built image (built just using docker) is only
6GB anyway.
My Dockerfile uses another image we made, so I'm trying to replicate this
problem with a simpler config, and will post shortly.
--
You received this message because you are subscribed to the Google Grou
Hi Matt,
Just as a check, you gave my suggested 24 gigs, or more (just to be safe)?
Theoretically, you can go up to 1024, so trying with the max value just to
make sure 24 isn't just a bit "too tight" might be of use here. I based
myself on your docker info for 24 gigs, maybe you'll need slight
Thanks Patrice,
I tried upping the size but got the same result. Here's the output around one
of the errors with debug verbosity:
INFO: Image e8f0aff7d819 already pushed, skipping
INFO: Pushing
ERROR: Failed to generate layer archive: mkdir
/var/lib/docker/graph/_tmp/7ce1c1718f7a273b54fca0a
Hey Matt,
So looking a bit into this, my first guess would be that, while your PC has
enough room, the image built doesn't, so your "VM" doesn't have enough
memory even if your computer does.
Do you mind running gcloud preview app deploy (or run, for that matters)
with "--verbosity debug"?
In
Sure, here's my app.yaml file
###
runtime: python27
threadsafe: true
api_version: 1
vm: true
handlers:
- url: /.*
script: miru.api.app
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To unsubscribe from this group and stop r
Hi Matt,
Do you mind including your app.yaml as well so we can look into this?
Cheers!
On Wednesday, August 26, 2015 at 9:04:07 PM UTC-4, Matt Hanson wrote:
>
> Hello,
>
> I've got a VM built from a Dockerfile, the build all happens fine, both on
> it's own or if spawned by 'gcloud preview app
11 matches
Mail list logo
