Mohsin Zaidi

Hi @parv3213, can you please try this again with the latest `go-ipfs-daemon` image? We've just updated to a newer version of `kubo`. Also, thanks @pradel for the input!

Closing for now, until more data is available.

@bshambaugh, can you please check this box on your PR so I can run the test workflow? It might be called ["Allow edits and access to secrets by maintainers"](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork). 

> cc @ukstv @smrz2001 @bshambaugh > > is it possible to merge this still? we are moving key-did-resolver package to the dids repo, would be nice to merge/release here before...

> > @bshambaugh, can you please check this box on your PR so I can run the test workflow? It might be called ["Allow edits and access to secrets by...

@bshambaugh, in case additional changes are needed (hopefully not), it would be great if you could set `bshambaugh-merge` as your target branch, whether through re-opening this PR or a new...

@fhirfly, are you building the image yourself, or using one of our [published](https://hub.docker.com/r/ceramicnetwork/js-ceramic/tags) Docker images? I just ran `ceramicnetwork/js-ceramic:latest`, `docker exec`'d in, and saw IPFS running properly. Can you elaborate...

Thanks, @pradel. The underlying IPFS issue appears to be the same but the fix for this issue (to update `package.json`) will go in `js-ceramic`, while the fix for #2362 (to...

> Mine happens on Docker in Gcloud as well. Oh ok ☹️ Have you made sure to pull the latest image using `docker pull`?

FYI, the Ceramic image now uses kubo v0. 15.0.