remix indie stack: failed launch

Questions / Help
1

Hi I am trying to deploy on fly.io for the first time. It is just a boilerplate remix indie stack. This is the error I got when I ran fly launch

==> Creating release
Error Mounts source volume “data” does not exist

2

Depending on what you’re trying to do, either removing the [mounts] section from your fly.toml or provisioning a new volume should do the trick for this error you’ve posted (docs).

Can you share your app’s fly.toml or the guide you’re following? Probably missing a step or two.

3 
# fly.toml file generated for young-wave-2856 on 2023-03-04T16:34:44+08:00

app = "young-wave-2856"
kill_signal = "SIGINT"
kill_timeout = 5
processes = []

[experimental]
  allowed_public_ports = []
  auto_rollback = true
  cmd = "start.sh"
  entrypoint = "sh"

[mounts]
  destination = "/data"
  source = "data"

[[services]]
  internal_port = 8080
  processes = ["app"]
  protocol = "tcp"
  script_checks = []
  [services.concurrency]
    hard_limit = 25
    soft_limit = 20
    type = "connections"

  [[services.http_checks]]
    grace_period = "5s"
    interval = "10s"
    method = "get"
    path = "/healthcheck"
    protocol = "http"
    timeout = "2s"
    tls_skip_verify = false
    [services.http_checks.headers]

  [[services.ports]]
    force_https = true
    handlers = ["http"]
    port = 80

  [[services.ports]]
    handlers = ["tls", "http"]
    port = 443

  [[services.tcp_checks]]
    grace_period = "1s"
    interval = "15s"
    restart_limit = 0
    timeout = "2s"

This is it. It was auto generated. I just follow this guide and ran fly launch

4

Thanks for explaining. I have a volume by default when I launch for the first time right? Or maybe I need to configure something to match the volume? Do I need it?

5

Thanks so much. I fixed it. I ran fly volumes create data and it works. Appreciate your help!

1 Like
6

Glad you’re up and running. Note that, volumes aren’t free (iirc). Fly doesn’t charge upto $5 anyway (ref), so that’s there too.

Yes, there’s a ~6G partition (/ as ext4) for your docker image to inflate into, and a separate boot partition (as ext2?). Both these partitions are ephemeral, as in, they don’t survive app restarts.

Fly Volumes are “persistent” (survive app restarts but not host failures, though there exists daily automated snapshots which expire in 5 days) that get mounted (as specified in fly.toml) into your app’s VM. You’d use it typically to host a database or objects and such.

7

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