I receive this error when trying deploy a very simple Deno app:
~/C/p/aye-aye flyctl deploy
==> Verifying app config
--> Verified app config
==> Building image
==> Building image with Buildpacks
--> docker host: 20.10.12 linux aarch64
latest: Pulling from flyio/builder
Status: Image is up to date for flyio/builder:latest
bionic: Pulling from flyio/buildpack-stack-run
Status: Image is up to date for flyio/buildpack-stack-run:bionic
[detector] io.fly.deno 0.0.3
[analyzer] Previous image with name "registry.fly.io/aye-aye:cache" not found
[builder] ---> Deno Buildpack
[builder] ---> Downloading and extracting Deno
[builder] curl: (22) The requested URL returned error: 404
[builder] ERROR: failed to build: exit status 22
Error failed to fetch an image or build from source: executing lifecycle. This may be the result of using an untrusted builder: failed with status code: 7
The Buildpack would be nice, but other confused souls can use a simple Dockerfile like this:
# The port that your application listens to.
# Prefer not to run as root.
# # Cache the dependencies as a layer (the following two steps are re-run only when deps.ts is modified).
# # Ideally cache deps.ts will download and compile _all_ external files used in main.ts.
# COPY deps.ts .
# RUN deno cache deps.ts
# These steps will be re-run upon each file change in your working directory:
ADD . .
# Compile the main app so that it doesn't need to be compiled each startup/entry.
RUN deno cache server.ts
CMD ["run", "--watch", "--allow-net", "--allow-read", "./server.ts"]
Well, Fly’s all-in on Elixir+Phoenix at this point, much to my chagrin (: Although, it is to be expected that they’d choose integrate really well with fewer technology stacks, and not look to boil the ocean, as it were (at least not until they cross the chasm, I guess).