Deploying a go app

Hello there!
I am trying to deploy a go app.
This is the source code: GitHub - livekit/livekit: End-to-end stack for WebRTC. SFU media server and SDKs.
I am getting this error:

***v0 failed - Failed due to unhealthy allocations - no stable job version to auto revert to and deploying as v1 

Troubleshooting guide at https://fly.io/docs/getting-started/troubleshooting/
Error abort

I recently deployed a Swift Vapor app with no major issues. I have read the troubleshooting docs and I can’t find a way to successfully deploy it.

Can you share the fly.toml configuration and the full output of flyctl

here is the fly.toml

# fly.toml file generated for lvkit on 2022-10-06T21:16:25+03:00

app = "lvkit"
kill_signal = "SIGINT"
kill_timeout = 5
processes = []

[env]

[experimental]
  allowed_public_ports = []
  auto_rollback = true

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

  [[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"

I am now getting a different Error. see the image.

What port do you have this configured to listen on (in your application)? You’ve got fly.toml looking for it on TCP port 8080, but the default configuration for this project doesn’t listen on that port.

The application uses 7880. Getting the error:

An existing fly.toml file was found for app lvkit
App is not running, deploy...
Deploying lvkit
==> Validating app configuration
--> Validating app configuration done
Services
TCP 80/443 ⇢ 7880
Error error connecting to docker: failed building options: failed probing "personal": context deadline exceeded

This is what I am getting.


Recent Logs
2022-10-06T18:57:21.000 [info] 2022/10/06 18:57:21 listening on [fdaa:0:b341:a7b:d6e9:83a:50c2:2]:22 (DNS: [fdaa::3]:53)
2022-10-06T18:57:21.000 [info] 2022-10-06T18:57:21.232Z	INFO	livekit	routing/interfaces.go:102	using single-node routing
2022-10-06T18:57:21.000 [info] one of key-file or keys must be provided in order to support a secure installation
2022-10-06T18:57:22.000 [info] Starting clean up.
2022-10-06T18:57:28.000 [info] Starting instance
2022-10-06T18:57:28.000 [info] Configuring virtual machine
2022-10-06T18:57:28.000 [info] Pulling container image
2022-10-06T18:57:29.000 [info] Unpacking image
2022-10-06T18:57:29.000 [info] Preparing kernel init
2022-10-06T18:57:29.000 [info] Configuring firecracker
2022-10-06T18:57:29.000 [info] Starting virtual machine
2022-10-06T18:57:29.000 [info] Starting init (commit: 249766e)...
2022-10-06T18:57:29.000 [info] Preparing to run: `/livekit-server` as root
2022-10-06T18:57:29.000 [info] 2022/10/06 18:57:29 listening on [fdaa:0:b341:a7b:d6e9:83a:50c2:2]:22 (DNS: [fdaa::3]:53)
2022-10-06T18:57:30.000 [info] 2022-10-06T18:57:30.018Z	INFO	livekit	routing/interfaces.go:102	using single-node routing
2022-10-06T18:57:30.000 [info] one of key-file or keys must be provided in order to support a secure installation
2022-10-06T18:57:30.000 [info] Starting clean up.
2022-10-06T18:57:37.000 [info] Starting instance
2022-10-06T18:57:37.000 [info] Configuring virtual machine
2022-10-06T18:57:37.000 [info] Pulling container image
2022-10-06T18:57:38.000 [info] Unpacking image
2022-10-06T18:57:38.000 [info] Preparing kernel init
2022-10-06T18:57:38.000 [info] Configuring firecracker
2022-10-06T18:57:38.000 [info] Starting virtual machine
2022-10-06T18:57:38.000 [info] Starting init (commit: 249766e)...
2022-10-06T18:57:38.000 [info] Preparing to run: `/livekit-server` as root
2022-10-06T18:57:38.000 [info] 2022/10/06 18:57:38 listening on [fdaa:0:b341:a7b:d6e9:83a:50c2:2]:22 (DNS: [fdaa::3]:53)
2022-10-06T18:57:38.000 [info] 2022-10-06T18:57:38.826Z	INFO	livekit	routing/interfaces.go:102	using single-node routing
2022-10-06T18:57:38.000 [info] one of key-file or keys must be provided in order to support a secure installation
2022-10-06T18:57:39.000 [info] Starting clean up.
***v1 failed - Failed due to unhealthy allocations - no stable job version to auto revert to and deploying as v2 

Troubleshooting guide at https://fly.io/docs/getting-started/troubleshooting/
Error abort


From How To to Questions / Help

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