Fly Apps on machine prerelease

[catflydotio]

You’d still get a Nomad (V1) app as of today, unless you used --force-machines with fly launch (or fly deploy, if you didn’t deploy straight from fly launch).

Right now there’s a manual step to enable you to create dedicated VMs. We’re working on making that a smoother experience while keeping a grip on the amount of compute abuse.

[pier]

Hey.

I updated my previous post but I did try with fly launch --force-machines and then fly launch --force-machines.

I still get Platform = nomad.

Edit:

Maybe it’s because I’m not deploying when launching?

I need to set up some secrets for the app to work. Would be great if I could do that when launching!

Edit:

It worked now!

I think the only thing I changed was turning off Docker desktop and building with the Fly builder?

[catflydotio]

@pier

I think the only thing I changed was turning off Docker desktop and building with the Fly builder?

If you can reproduce, we’d love a bug report on flyctl GitHub - superfly/flyctl: Command line tools for fly.io services

[pier]

I will try to reproduce and file a bug if that’s the case.

BTW

The dashboard and fly status don’t show the same info for machines.

Machines
ID            	PROCESS	VERSION	REGION	STATE  	HEALTH CHECKS     	LAST UPDATED
4d891159b55987	app    	1      	dfw   	started	1 total, 1 passing	2023-03-01T15:26:36Z

Also, I created the app in QRO but apparently the machine was deployed to DFW. Not sure why since QRO is much closer to me.

Edit:

So I created a new app with Docker desktop and it worked. Not sure what happened before.

Now the dashboard and the CLI do show the same machine ID but still the machine was deployed to DFW instead of QRO. The app was configured in QRO:

Region Pool:
qro

Edit:

Regarding the discrepancy between the dashboard and the CLI. I’m an idiot. I was looking at another app. Sorry.

[catflydotio]

Thanks!

Apps V2 doesn’t use region pool. Machines VMs are tied to hardware, so you specify the region for each one. To note: Apps V2 isn’t fully cooked. Bug reports are welcome for unexpected UX!

[pier]

BTW I have to say that v2 apps are fast!

The builder launches super fast, it feels as if I was using Docker desktop. Same with deploying and managing.

Bravo

[Alex21]

With the announcement in Make Apps V2 the default for new apps in your org, is there any capability related to appsv2 that requires the flyctl prerelease, or is everything from this post all now available in the mainline flyctl version?

[catflydotio]

Hi @Alex21! It’s all in the main flyctl release now. If you’re trying out Apps V2 keep an eye on the latest releases because it’s moving fast. Latest as I type is v0.0.482.

[rodolfosilva]

@tvdfly

Migrating existing apps

If you already have an app with machines, running fly deploy will convert it to an apps v2 app. You’ll be prompted to do the migration.

We don’t currently support migrating apps from Nomad to Machines. We’ll announce when that’s available.

Note/Warning this will overwrite the config for all these machines, based on the values set in fly.toml and the existing config on the machines. As an example, the services and environment values will come from fly.toml replacing whatever was present before. Any mounts will not change, though fly deploy may change the mount path if the destination path under the [mounts] section in fly.toml is different than what’s currently on a machine.

Is there any prediction of when we will have this? Apparently there is no way with nomad to have shared-cpu-2x, shared-cpu-3x, shared-cpu-4x.

[billy]

We’re currently hard at work to get it shipped as soon as possible.