Help running livebook on Fly

Questions / Help
,
1

I used livebook 0.12.1 on fly previously, using the approach set out here: Deploy Livebook on Fly.io · Fly Docs

But now, trying the same approach with the latest version of livebook, I get an error in the UI whenever I try to execute a cell:

Connecting runtime failed - Elixir terminated unexpectedly, please check your logs for errors. Reason: normal

Any ideas what I might be missing? This is my fly.toml:

[build]
  image = 'ghcr.io/livebook-dev/livebook'

[env]
  ELIXIR_ERL_OPTIONS = '-proto_dist inet6_tcp'
  LIVEBOOK_DATA_PATH = '/data'
  LIVEBOOK_HOME = '/data'
  LIVEBOOK_IP = '::'
  LIVEBOOK_ROOT_PATH = '/data'
  PORT = '8080'

[[mounts]]
  source = 'data'
  destination = '/data'
  initial_size = '10gb'

[http_service]
  internal_port = 8080
  force_https = true
  auto_stop_machines = 'off'
  auto_start_machines = false
  min_machines_running = 0
  processes = ['app']

[[vm]]
  memory = '1gb'
  cpu_kind = 'shared'
  cpus = 1
2

P.S. I don’t see anything obvious in the logs, this is what ‘fly logs’ is giving me:

2024-09-09T14:48:46Z runner[e286759ec47098] lax [info]Configuring firecracker
2024-09-09T14:48:46Z app[e286759ec47098] lax [info]BREAK: (a)bort (A)bort with dump (c)ontinue (p)roc info (i)nfo
2024-09-09T14:48:46Z app[e286759ec47098] lax [info]       (l)oaded (v)ersion (k)ill (D)b-tables (d)istribution
2024-09-09T14:48:46Z app[e286759ec47098] lax [info][os_mon] memory supervisor port (memsup): Erlang has closed
2024-09-09T14:48:46Z app[e286759ec47098] lax [info] INFO Main child exited normally with code: 0
2024-09-09T14:48:46Z app[e286759ec47098] lax [info] WARN Reaped child process with pid: 389 and signal: SIGUSR1, core dumped? false
2024-09-09T14:48:46Z app[e286759ec47098] lax [info] WARN Reaped child process with pid: 432 and signal: SIGUSR1, core dumped? false
2024-09-09T14:48:46Z app[e286759ec47098] lax [info] INFO Starting clean up.
2024-09-09T14:48:46Z app[e286759ec47098] lax [info] INFO Umounting /dev/vdc from /data
2024-09-09T14:48:46Z app[e286759ec47098] lax [info][  397.135387] reboot: Restarting system
2024-09-09T14:48:49Z app[e286759ec47098] lax [info][    0.276143] PCI: Fatal: No config space access function found
2024-09-09T14:48:49Z app[e286759ec47098] lax [info] INFO Starting init (commit: 20f21dc5f)...
2024-09-09T14:48:49Z app[e286759ec47098] lax [info] INFO Mounting /dev/vdc at /data w/ uid: 0, gid: 0 and chmod 0755
2024-09-09T14:48:49Z app[e286759ec47098] lax [info] INFO Resized /data to 10720641024 bytes
2024-09-09T14:48:49Z app[e286759ec47098] lax [info] INFO Preparing to run: `/app/bin/server` as root
2024-09-09T14:48:49Z app[e286759ec47098] lax [info] INFO [fly api proxy] listening at /.fly/api
2024-09-09T14:48:49Z app[e286759ec47098] lax [info]2024/09/09 14:48:49 INFO SSH listening listen_address=[fdaa:9:1da7:a7b:2b9:5434:ebe0:2]:22 dns_server=[fdaa::3]:53
2024-09-09T14:48:49Z runner[e286759ec47098] lax [info]Machine created and started in 3.94s
2024-09-09T14:48:50Z app[e286759ec47098] lax [info][Livebook] Application running at http://localhost:8080/
2024-09-09T14:48:50Z app[e286759ec47098] lax [info] WARN Reaped child process with pid: 380 and signal: SIGUSR1, core dumped? false
2024-09-09T14:49:32Z app[e286759ec47098] lax [info] WARN Reaped child process with pid: 420 and signal: SIGUSR1, core dumped? false
2024-09-09T14:49:43Z app[e286759ec47098] lax [info] WARN Reaped child process with pid: 422 and signal: SIGUSR1, core dumped? false
3

We no longer pass ELIXIR_ERL_OPTIONS to the runtime node. Please change ELIXIR_ERL_OPTIONS to ERL_AFLAGS and try again. The Fly guide has been updated to do that : )

1 Like
4

That was it. Thanks @jonatanklosko !

1 Like