3 ms·
Spent last night migrating a Discord bot from Heroku to Fly as a result of the upcoming closure of the Heroku free dynos. Overall fairly painless, though I opte
by mroche 4y ago
Spent last night migrating a Discord bot from Heroku to Fly as a result of the upcoming closure of the Heroku free dynos. Overall fairly painless, though I opted to provide my own images rather than use a source-to-image pipeline and discovered one little quirk: images require a Docker V2 formatted manifest. I use Buildah and Podman in my workflows which default to the OCI format. This was simple enough to solve once I figured it out, but I only found one or two forum posts on it and spent a lot of time trying to figure out why the deployment couldn't find an image that I manually pushed to registry.fly.io.
- bongobingo1 4y agoFor others, you can adjust the format with `podman build --format=docker` (or set `BUILDAH_FORMAT=docker`) or possibly you can push it separately? https://docs.podman.io/en/latest/markdown/podman-manifest-push.1.html https://docs.podman.io/en/latest/markdown/podman-manifest-pu... Wonder why they don't use OCI format.
- mroche 4y agoYeah, I use Buildah for creating my images, so the environment variable or specifying commit --format docker would work. Before I did that I just re-pushed the image itself using the v2s2 format, so: # podman inspect quay.io/my/image:latest | jq ".[].ManifestType" "application/vnd.oci.image.manifest.v1+json" # podman push --format v2s2 quay.io/my/image:latest registry.fly.io/my-app:latest
- deleted 4y ago[deleted]