-
Notifications
You must be signed in to change notification settings - Fork 127
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ceramic Daemon fails to start IPFS in Docker container #2341
Comments
@fhirfly, are you building the image yourself, or using one of our published Docker images? I just ran Can you elaborate the steps you used when you saw this issue?
|
Mine happens on Docker in Gcloud as well.
On Mon, Aug 8, 2022 at 11:42 AM Léo Pradel ***@***.***> wrote:
It looks like #2362
<#2362> is a duplicate
of this one, @smrz2001 <https://github.com/smrz2001> I think that the
issue is happening on mac m1
—
Reply to this email directly, view it on GitHub
<#2341 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATDYKHVILZUQNWZ66U6IDP3VYETGNANCNFSM547JYBVQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Richard Braman
FHIRFLY
v: 252-947-1035
Fly Health, LLC
<https://www.fhirfly.io/ipfs/QmSSyHvwbpry3QTMYCy86uQCMoKVNjRDykrUeogZo9cjAK/fhir/r4/Organization/did:ens:fhirly.eth>
https://fly.health
|
Oh ok |
FYI, the Ceramic image now uses kubo v0. 15.0. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Ceramic Daemon fails to start IPFS in Docker container. This is a known issue: ipfs/kubo#8704. This applies to docker environments like Google cloud run. You need to bump to ipfs daemon go-ipfs to version .13
To Reproduce
Steps to reproduce the behavior:
Try to start ceramic daemon on a docker container, IPFS will fail
Expected behavior
ceramic daemon starts with no errors on Docker
Screenshots
If applicable, add screenshots to help explain your problem.
Ceramic versions
cli 2.4
Machine, OS, browser information (please complete the following information):
2022-07-29T02:52:32.327905Z stdout: 'Initializing daemon...\n' +
Default
2022-07-29T02:52:32.327916Z 'go-ipfs version: 0.12.2\n' +
Default
2022-07-29T02:52:32.327942Z 'Repo version: 12\n' +
Default
2022-07-29T02:52:32.327952Z 'System version: amd64/linux\n' +
Default
2022-07-29T02:52:32.327963Z 'Golang version: go1.16.15\n',
Default
2022-07-29T02:52:32.327976Z stderr: '2022/07/29 02:52:32 [zeroconf] no suitable IPv4 interface: udp4: failed to join any of these interfaces: []\n' +
Default
2022-07-29T02:52:32.327999Z '2022/07/29 02:52:32 [zeroconf] no suitable IPv6 interface: udp6: failed to join any of these interfaces: []\n' +
Default
2022-07-29T02:52:32.328011Z '2022-07-29T02:52:32.272Z\tERROR\tcmd/ipfs\tipfs/daemon.go:430\terror from node construction: no supported interface\n' +
The text was updated successfully, but these errors were encountered: