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 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:
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.
The text was updated successfully, but these errors were encountered:
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 thestorage.PutFS(storage.IndexDirName, storage.IndexArchiveName)
call, when that function reaches this line:This is the error that is returned:
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
.The text was updated successfully, but these errors were encountered: