Goroutine dump with Coder V2 on Fly.io
Hey all!
I'm deploying Coder to Fly.io, with an external database, following this (https://coder.com/blog/remote-developer-environments-on-fly-io) guide.
I'm getting a very long Goroutine dump, and it goes on for around ~40-50 lines.
I will try and get a sample after dinner, and sanitise it.
However, I was wondering if anyone else using Fly had a similar issue?
Thanks!
Coder
Remote developer environments on Fly.io
Coder moves developer workspaces off local machines and into your cloud infrastructure, centralizing their management and safeguarding your code and data.
18 Replies
<#1217203906979954709>
Category
Bug report
Product
Coder OSS (v2)
Platform
Linux
Logs
Please post any relevant logs/error messages.
Got some logs. I'm not really sure where the cause is here:
Apologies for the huge block, it goes on for some length.
where do these logs come from ?
the workspace build logs ?
I'm deploying to Fly.io via that post I linked to. These logs come from the container startup of the base Coder instance.
There's a lot of lines, and I'm not sure where the dump starts from. I could probably do a
tee
invocation to log it all.
(I'm using Coder V2)oh okay, I understood that you were deploying your workspaces on fly.io, not Coder on fly.io
could you try getting the full logs please ?
I've just tried again - I get a bit further this time. My guess is that when Coder can't connect to Postgres (pubsub?), all comes crashing down.
I'm now on the login screen, but my original attempt was to use 6PN to access Coder. I don't want it public.
I can't get all of the logs though. The buffer is full.
is there some way you could get it to log to a file or something like that ?
hmm, that's weird, it definitely shouldn't crash like that
OK. So I've figured out that if I set the base URL to
http://app_name.internal
, it crashes. That also happens with HTTPS.
If you use .fly.dev
, it works. I've attached as much logs I've got here:.internal
should work fine if it uses the Fly DNS, because it'll just resolve to the 6PN IPv6 address.
But I'm not sure the way this goroutine is handled is quite right though...yeah and it really shouldn't crash like that
could you create an issue over @ coder/coder to explore the root cause of this bug ?
Yes please create an issue and we can see how we can improve the experience in this case.
hey @Dom R (shymega), did you get the time to create an issue for this ? that way we can reference it here
I haven't yet had the time. Problem is, I don't think Coder officially supports Fly.io anymore (not helped by Fly discontinuing their TF provider), and I'm not sure if this issue will have much traction.
I've got it on my todo list though.
Hey, so I tried to replicate the bug - at last! - and so far so good. I've managed to create a user. I don't know if Coder does still support Fly, but we'll see how I get on.
hey!
well technically there isn't "official support" or not (except for integrations with partners)
so long as Terraform supports Fly, then Coder should support it too!
oh, well, you are right
the Terraform provider for Fly.io was dropped by Fly
https://community.fly.io/t/fresh-produce-volumes-endpoints-in-machines-api/14408/20
Fly.io
[Fresh Produce] Volumes endpoints in Machines API
Hi @charsleysa, I think the best answer I can give for this is that the community is welcome to fork the fly-apps Terraform provider. I can appreciate that this is not the most satisfying answer, given that we also don’t promise never to pick this up again. Ultimately it’s code that handles users’ API keys. There’s an expectation that we’d ensu...
I will close this thread since there is nothing we can do about it, though let's continue discussing this through your GH issue so that we can avoid misunderstandings in the future :)
GitHub
Add warning to documentation for Fly.io · Issue #14599 · coder/coder
I am under the impression that Fly.io is no longer supported by Coder because of the unmaintained Terraform provider. This issue is to track the progress of adding a deprecation warning to the docu...
@Phorcys closed the thread.