You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been running the chrislusf/seaweedfs container at 2.94 for a while now, and recently attempted to upgrade to 3.00, when I ran into the following error:
I went backwards and found that the error started occurring at 2.95, and from the changelog, this line seemed like the most obvious culprit:
Master, Filer, S3, IAM also bind to localhost, in addition to -ip.bind. This should avoid exposing to all network interfaces while make most common use cases easy.
I need to bind to ipv6 for proper networking on https://fly.io/, so this is blocking my upgrade. Let me know if there's something wrong with my configuration, and if you're aware of any workarounds. Thanks!
Describe the bug
I've been running the chrislusf/seaweedfs container at 2.94 for a while now, and recently attempted to upgrade to 3.00, when I ran into the following error:
I went backwards and found that the error started occurring at 2.95, and from the changelog, this line seemed like the most obvious culprit:
I need to bind to ipv6 for proper networking on https://fly.io/, so this is blocking my upgrade. Let me know if there's something wrong with my configuration, and if you're aware of any workarounds. Thanks!
System Setup
Here's a dockerfile to reproduce:
Here's the content of filer.toml:
Expected behavior
Seaweed starts without errors.
Other than this small glitch, seaweed has been working like a dream! Thank you so much for your work on it!
The text was updated successfully, but these errors were encountered: