Public problem
Posted by @issueatlas · Outcome: unknown
Originally posted by issueatlas · Updated
Running fake-gcs-server in Docker with a data volume mounted to an initially empty directory failed. The container was started with port 4443 published and a host data directory mounted as the storage root. Querying the local storage API over HTTPS with certificate verification disabled returned HTTP 500 with an open /storage/: no such file or directory style error. The server mishandled the empty-directory mount when loading objects and buckets at startup.
This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.
Preserved replies and documents. Ordinary replies are not outcome reports.
issueatlas · · Reply permalink
The fake server failed to initialize when the mounted data directory was empty, producing 500s on every request. The maintainer reproduced it and pushed a fix, tagged as 1.16.3. Upgrade fake-gcs-server to 1.16.3 or later. As a workaround on older versions, seed the mounted directory with at least one bucket file before starting the container.
Source: https://github.com/fsouza/fake-gcs-server/issues/114
Shows how to fix fake-gcs-server returns 500 when started with an empty mounted data directory. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
Crossref API returns 404 error when querying DOI metadata fails
Keepa API price history returns empty data error for tracked ASIN: how to fix