Livebook launcher created 'machines that aren't part of the Fly Apps Platform'?

,
1

The Livebook launcher, run late yesterday against what I can see is v0.11.0, appears to have created machines that aren’t part of the Apps platform.

➜  fly status --app=bar
App
  Name     = bar
  Owner    = foo
  Hostname = bar.fly.dev
  Image    = -
  Platform = machines

Found machines that arent part of the Fly Apps Platform, run fly machines list to see them.

This complicates scaling. The 256mb instance literally crashes trying to install the dependencies for the DB connector cell, but you can’t use the CLI scale commands to bump up memory because:

➜  fly scale vm shared-cpu-2x --app bar
Error: No active machines in process group 'app', check `fly status` output

fly m list shows the following:

1 machines have been retrieved from app bar.
View them in the UI here

bar
ID            	NAME            	STATE  	REGION	IMAGE                       	IP ADDRESS                     	VOLUME              	CREATED             	LAST UPDATED        	APP PLATFORM	PROCESS GROUP	SIZE
9080516fe39587	black-paper-2060	started	dfw   	livebook-dev/livebook:0.11.0	fdaa:2:58d7:a7b:a062:7bc2:aaf:2	vol_545z5996x0061xq4	2023-10-11T15:11:50Z	2023-10-11T15:12:09Z	            	             	shared-cpu-1x:256MB

More things I tried that don’t work:

  • fly app restart bar
  • ‘fly deploy with the livebook image’ – from a forum thread about doing that to redeploy it, which un-blocked someone, but that magic snippet for deploying with the ghcr.io image didn’t work for me
1 Like
2

Thanks for sharing that!

I will be updating our launcher shortly to fix that for new deployments.

In the meantime you can fix your current machine by running:

fly -a YOUR_APP_NAME m update YOUR_MACHINE_ID --metadata fly_platform_version=v2 --metadata fly_process_group=app
3

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.