Using the Fly Docker registry#

Tagging images for the Fly registry#

Fly’s registry is called registry.fly.io. To use it, you need to tag your Docker images with a tag that begins with that string.

Every Fly app gets its own registry subdomain. You can create apps in a number of ways, but the easiest is to use the Fly CLI:

1
flyctl apps create datasette-demo

Fly app names must be globally unique across all of Fly - you will get an error if the app name is already taken.

You can create an app with a random, freely available name using the --generate-name option:

1
~ % flyctl apps create --generate-name
2
? Select Organization: Simon Willison (personal)
3
New app created: rough-dew-1296

Now that you have an app name, you can tag your Docker image using:

1
registry.fly.io/your-app-name:unique-tag-for-your-image

If you are building an image using Docker on your machine, you can run this command in the same directory as your Dockerfile:

1
docker build -t registry.fly.io/datasette-demo:datasette-demo-v0 .

Pushing images to the registry#

In order to push your image to Fly, you will first need to authenticate.

The flyctl auth docker command will do this for you:

1
~ % flyctl auth docker
2
Authentication successful. You can now tag and push images to registry.fly.io/{your-app}

This works by hooking into Docker’s own authentication mechanism. You can see what it has done by looking at your ~/.docker/config.json file. Mine looks like this:

1
{
2
  "auths": {
3
    "registry.fly.io": {
4
      "auth": "... secret token here ..."
5
    }
6
  ,
7
  "experimental": "disabled",
8
  "stackOrchestrator": "swarm"
9
}

Now you can push your image to the registry like this:

1
docker push registry.fly.io/datasette-demo:datasette-demo-v0

Deploying an image#

Now that your image is pushed, you can deploy an instance of it like this:

1
flyctl deploy --app datasette-demo \
2
  --image registry.fly.io/datasette-demo:datasette-demo-v0

A few seconds later your app will be running at:

1
https://name-of-your-app.fly.dev/