Skip to content
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

With both dataservice and fake-gcs-server running in docker, store.PutFS() on the index fails. #1

Open
wintermute-cell opened this issue Feb 28, 2024 · 0 comments

Comments

@wintermute-cell
Copy link
Owner

I don't know what's happening here, any suggestions or contributions welcome!

Description

When running both the dataservice and the fake-gcs-server as docker containers, in a shared network, the dataservice's fetchAndStoreAssets() errors in the storage.PutFS(storage.IndexDirName, storage.IndexArchiveName) call, when that function reaches this line:

obj := bkt.Object(nameInStorage)
w := obj.NewWriter(ctx)
if _, err := w.Write(archiveBytes); err != nil {
    return fmt.Errorf("Writer.Write: %v", err)    // <- error happens here
}

This is the error that is returned:

Post "http://0.0.0.0:4443/upload/storage/v1/b/itchgrep-data/o?uploadType=resumable&name=index.bleve.gz.tar&upload_id=3ea72214406f9c4c91a02539b9a0fe8b": dial tcp 0.0.0.0:4443: connect: connection refused

This behaviour can be observed when locally running the setup with task local-dataservice.

Findings so far

It seems like this issue is somehow caused by the interaction with Docker.
When the dataservice is not running in a docker container, the problem does not occur, and the index is stored on the fake-gcs-server just fine.

As a temporary solution, the dataservice can be run this way using task local-dataservice-temp-fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant