App Platform App Spec with Image

Question

I am currently trying to deploy a existing container image to app platform

I created a repository with nothing but the file .do/app.yaml, contents:

name: sample-metabase
services:
- name: metabase-app
  image:
    registry_type: "UNSPECIFIED"
    registry: "hub.docker.com"
    repository: "metabase/metabase"
    tag: "v0.37.2"
  instance_size_slug: "basic-xxs"
  instance_count: 1
  http_port: 3000
  routes:
  - path: /

From my, limited, understanding this should work. However app platform tells me “We’re sorry, but we weren’t able to detect anything that the App Platform can currently run in the repository you selected. Please try a different repository.” - What am I missing?

Answer 1

ntate December 2, 2020

Currently, only DigitalOcean Container Registries (DOCR) registries are supported as an image source type. If you were to upload your metabase:v0.37.2 to your DOCR registry, you could reference it as follows:

name: sample-metabase
services:
- name: metabase-app
  image:
    registry_type: "DOCR"
    repository: "metabase"
    tag: "v0.37.2"
  instance_size_slug: "basic-xxs"
  instance_count: 1
  http_port: 3000
  routes:
  - path: /

We automatically infer the registry associated with your account and handle credential management.

Public Dockerhub image support is on the roadmap and will be available in the near future. Additionally, I will open up an internal support ticket to better handle the failure messaging in this case to make it more clear.

Reply Report

mhubert December 28, 2020

Error still is not clear, also in your documentation ( https://www.digitalocean.com/docs/app-platform/references/app-specification-reference/ ) you should state that using services.image.registry is unsupported. Just lost two hours debugging it …
Reply Report
- willowbrae February 18, 2021
  
  I had this same problem too. It turned out that my issue was that I was running an older version of doctl CLI (1.48.0 instead of 1.56.0). Everything worked after that. Here is what it looks like for Hasura, I’m sure metabase is similar:
  
  name: hasura region: sgp1 services: - name: hasura image: registry_type: DOCKER_HUB registry: docker.io repository: hasura/graphql-engine http_port: 8080
  
  Reply Report
  
  willowbrae February 18, 2021
  
  Actually, I’m sorry — this fixed the CLI bugging out but didn’t actually deploy. I had pull from docker hub and push into my private DO registry as per these instructions: https://www.digitalocean.com/community/questions/how-do-i-uload-my-docker-image-to-digital-ocean
  
  I can probably automate this for now but it would be nice if pulling public images from Docker Hub would just work.
  
  Reply Report
  
  digitaloceancomSquid August 5, 2021
  
  Has this been fixed yet?
  
  I’m looking here, and there just no explanations, and the error messages aren’t helpful at all.
  
  https://cloud.digitalocean.com/apps/new?i=a4970b
  
  And it specifically says its using docker hub, but I can’t figure out the format.
  
  Reply Report

Answer 2

mhubert December 28, 2020

Error still is not clear, also in your documentation ( https://www.digitalocean.com/docs/app-platform/references/app-specification-reference/ ) you should state that using services.image.registry is unsupported. Just lost two hours debugging it …
Reply Report
- willowbrae February 18, 2021
  
  I had this same problem too. It turned out that my issue was that I was running an older version of doctl CLI (1.48.0 instead of 1.56.0). Everything worked after that. Here is what it looks like for Hasura, I’m sure metabase is similar:
  
  name: hasura region: sgp1 services: - name: hasura image: registry_type: DOCKER_HUB registry: docker.io repository: hasura/graphql-engine http_port: 8080
  
  Reply Report
  
  willowbrae February 18, 2021
  
  Actually, I’m sorry — this fixed the CLI bugging out but didn’t actually deploy. I had pull from docker hub and push into my private DO registry as per these instructions: https://www.digitalocean.com/community/questions/how-do-i-uload-my-docker-image-to-digital-ocean
  
  I can probably automate this for now but it would be nice if pulling public images from Docker Hub would just work.
  
  Reply Report
  
  digitaloceancomSquid August 5, 2021
  
  Has this been fixed yet?
  
  I’m looking here, and there just no explanations, and the error messages aren’t helpful at all.
  
  https://cloud.digitalocean.com/apps/new?i=a4970b
  
  And it specifically says its using docker hub, but I can’t figure out the format.
  
  Reply Report

Related

Question

App Platform App Spec with Image

Related

Leave a comment

Looking for something else?

Sign up for our newsletter

Related

Question

App Platform App Spec with Image

Related

Leave a comment

Related

question

Why am I getting a Deploy Error: Health Checks?

question

How can I see the build logs for my application if the build was skipped for a deployment?

question

How can I use private git submodules in my app?

question

What does a "Development Database" mean in the context of the App Platform?

Looking for something else?