deployment failed : [3] Only Docker v2 images can be deployed to the Flexible environment

[ta...@freightos.com]

I started to see new error that appeared few days ago when trying to deploy to flexible environment as following :

[INFO] Updating module [backend]...\
[INFO]                              
[INFO] Updating module [backend]...|
[INFO]                              
[INFO] Updating module [backend].../
[INFO]                              
[INFO] Updating module [backend]...failed.
[INFO] ERROR: (gcloud.preview.app.deploy) Error Response: [3] Only Docker v2 images can be deployed to the Flexible environment.
[ERROR] Error: gcloud app command with exit code : 1
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE

I am using gcloud sdk version 103.0.0

Any idea why that error appeared ?

Thanks

[Rodrigo De Castro]

Please update your gcloud and this error should go away (let us know otherwise).

The context is that we're rolling out a change to block Docker v1 (as announced here) and older versions of gcloud that upload to the v1 repository will no longer work.

--
You received this message because you are subscribed to the Google Groups "google-cloud-sdk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-s...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-cloud-sdk.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sdk/ac27d8bd-3cae-4ffe-b2ad-7f2e421a275f%40googlegroups.com.

[Christopher Bourez]

In my case, I forgot to upload the image to registry. There was no docker image to which I was pointing. 

The message is not clear.

[Rodrigo De Castro]

Thanks, Christopher. After investigation another report, we realized that this message is being returned for issues not related to Docker version. We have a bug open to improve that message for those use cases.

--
You received this message because you are subscribed to the Google Groups "google-cloud-sdk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-s...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-cloud-sdk.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sdk/577987f0-4072-4684-8d7a-67aa7d027198%40googlegroups.com.

[Matt Mohebbi]

I'm seeing this issue as well. We have been testing deploying a node application to iodine-test (a project we created recent for testing purposes). Now that things are working well, we want to push to the iodine-prod project but we are getting this same error:

latest: digest: sha256:77a54d00e30ac7ba565a9a545a7bf57677f4baa4f8bd8f7ed641488c63d96e35 size: 39006

DONE

----------------------------------------------------------------------------------------------------------------------------------

Updating service [default]...failed.

ERROR: (gcloud.app.deploy) Error Response: [3] Only Docker v2 images can be deployed to the Flexible environment.

I updated to the latest gcloud components and I'm still getting this error. Here's the version info:

air:/tmp/plum/deploy-20160727-124350% gcloud --version

Google Cloud SDK 119.0.0

beta 2016.01.12

bq 2.0.24

bq-nix 2.0.24

core 2016.07.21

core-nix 2016.03.28

gcloud 

gsutil 4.19

gsutil-nix 4.18

kubectl 

kubectl-darwin-x86_64 1.2.5

One bit of context that may be helpful is that we did try using node on appengine with the beta back in Spring of 2015 with this project. Perhaps there is something lingering as a result of that?

Thanks,

Matt

[Jayant Shukla]

Same thing here , I tried the same loopback node.js app on compute engine and it works fine , but while try to deploy on gae i get this

Updating service [default]...failed.
ERROR: (gcloud.app.deploy) Error Response: [3] Only Docker v2 images can be deployed to the Flexible environment.

tried with both gcloud 118 and gcloud 119.

[Rodrigo De Castro]

This error message can be misleading, as other issues might also result in the same error you are seeing.

In the case below (about test and prod projects), it seems it could be a permission issue. You need to make sure that the prod project has access to the GCS container holding the image you are deploying - assuming here you're just using image_url to deploy.

About Jayant's case, I'd make sure that this is a Docker v2 image. If you have it locally, please use the latest gcloud and push it to the GCR repository (using your own project for storing it) and reference that. 

Jayant - can you also please share the Docker image just so we validate whether it might be a Docker v1 and needs to be updated?

To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sdk/b7f75de0-9d16-4a44-b839-61ba5143fd30%40googlegroups.com.

[Matt Mohebbi]

I think it's unlikely to be a permissions problem. Both the pushes were started from scratch using the gcloud app deploy command. E.g. New docker images were created and pushed. Can you think of anything else that could be going on? Is there a way to get a better error messages (perhaps a verbose mode?) if this one is misleading?

You received this message because you are subscribed to a topic in the Google Groups "google-cloud-sdk" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-cloud-sdk/jDsIYukZ9LU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-cloud-s...@googlegroups.com.

Visit this group at https://groups.google.com/group/google-cloud-sdk.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sdk/CAOH6srm6LKg4f_KTN%2B-O0UfQizjDkUO3kTcSNBX4xZG%2BDh62JA%40mail.gmail.com.

[Rodrigo De Castro]

Could you please provide the app? Is it iodine-prod? When did you try to deploy last? I couldn't find recent deployments for iodine-prod, so just want to double check.

[Matt Mohebbi]

It is iodine-prod. You should be able to see the image in the cloud builder. After the image has been built, the deploy process starts with the spinner but after a few seconds it bails with the version error. Thus it doesn't get far enough along to even be registered in appengine. If you look at iodine-test you can see a successful deploy yesterday.

[sbe...@small-improvements.com]

I'm experiencing the same issue right now. Interestingly, my colleague is able to deploy our app. 

The only difference between us we can think of so far is that he is on Linux while I'm on OSX. We are both on gcloud 119.0.0.

Stephan

[ch...@xlevus.net]

I have just started to get this error on a project I created today.

I can run `gcloud app deploy` on one older project, but not another.

Running `gcloud components update` does not resolve the issue.

[ch...@xlevus.net]

Actually. My bad. Was trying to run container images on a bucket on another project.

Error message could be improved though.

[Matt Mohebbi]

That's good to know. I am on OSX as well. I'll also note that I created a brand new project over the weekend and was able to push to that project without a problem. This error is only happening with iodine-prod, where there was previously a standard python appengine application. 

--
You received this message because you are subscribed to a topic in the Google Groups "google-cloud-sdk" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-cloud-sdk/jDsIYukZ9LU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-cloud-s...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-cloud-sdk.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sdk/1aee034e-db1d-42d8-bd74-4af69432c631%40googlegroups.com.