Deploy Docker images from public & private registries | Feature Requests

186

Deploy Docker images from public & private registries

in progress

Kai Marshland

There are some images out there that I would like to be able to deploy in a single step, eg databases like https://hub.docker.com/_/neo4j/.

Or if I'm using GitHub/GitLab CI/CD, I should be able to pull my image directly from their registries with the appropriate credentials.

August 20, 2019

Jake Malachowski

Deploying images from registries is now in Early Access. You can deploy public images from any registry, and private images from Docker Hub, Github Container Registry, and GitLab Container Registry. Enable the feature from your user or team settings page to try it out.
Please share any questions or feedback by emailing deploy-from-registry-feedback@render.com
You can learn more about the feature here: https://render.com/docs/deploy-an-image

Alan Cohen

Jake Malachowski: Is it not possible to use this with existing projects?

Jake Malachowski

Alan Cohen: Not yet, but we're planning to add support for converting existing services to use images soon.

Alan Cohen

Jake Malachowski: That would be great. Right now the biggest issue we have is that our deployments take 10-15m, where most of that time is spent building a Docker image (and we're reusing the same image for multiple services). We can cut that down to 1-3 minutes if we could use our own build machines.

Meagan Gamache

marked this post as

in progress

Jared Mackey

Meagan Gamache: this made my whole day. 😁

Rolando Carias

Meagan Gamache: What is the timeframe for this?

Franklin Kumro Jr

How about an update on this Anurag Goel? Is this going to be a 3 year old request?

Nathan Woodhull

This is even more important for us now that render.com plans to charge for build minutes.

Benjamin Dobell

Would love to migrate across from fly.io, the experience with them has been nothing but trouble. That said, this is vital.

Actually, I don't even need render.com to pull from an external Docker registry. I just need to be able to push to the render.com registry, which is what we do with fly.io. Our CI builds our images.

Matt Joiner

Benjamin Dobell: what issues did you have with Fly.io? I'm worried too

Billy Irwin

Anurag Goel can we get an update on this one? Obviously I have no context to your infrastructure but deploying a docker image from a remote registry seem like low hanging fruit?

It also helps solve a number of other feature requests in the planned column since it allows us to just use our own build machines.

Steven Edouard

Another bump. I'm really surprised this doesn't already exist. It seems easier to deploy Docker apps from a registry rather than building them from Dockerfiles. It also makes any CI/CD workflow with Docker necessitate double-building (building in CI and in Render).

Billy Irwin

Bump on this. Would really like to use my own build machines to navigate a ton of other issues in the "Planned" sections.

I've had issues already with build timeouts, running out of memory, and random build errors that I can't repro locally via docker. This would resolve all of them

Franklin Kumro Jr

Where does this land priority wise in the ever growing list of "Planned" features? It would help if the list had some sort of priority. Thanks!

Emile

This would also be a decent patch for the crappy build machines. Currently releasing our rust backend takes more than 40m...

rik.huijzer

Emile: I had the same and just manged to work around it. In essence, the workaround is based on the fact that Render is not linked to private Docker repositories, but it is linked to private (Git) repositories. Therefore, to speed up the build: put prepared artifacts in a private repository and pick them up from there.
To do this, I'm now building the release binaries in a GitHub Action and push these to a separate branch just like static websites are (e.g., peaceiris/actions-gh-pages). After this, the Action calls the deploy API to trigger a deploy from the separate branch. 
The separate branch, at deployment, contains a Dockerfile, the binary, and possibly some more files which are needed in production. The Dockerfile is executed by Render and copies the files in. That's it. Takes about 3 Render build minutes per deploy.
Regarding the binaries, I was unable to create static binaries via musl in the Action. Therefore, I used dynamic binaries and ensured that the GitHub Action and Dockerfile both used the same Ubuntu version. That should work.

→