mirror of
https://github.com/fsouza/fake-gcs-server.git
synced 2026-04-27 22:55:50 +03:00
[GH-ISSUE #713] Failed to get object with error storage: object doesn't exist @ 1.37.0 #124
Labels
No labels
bug
compatibility-issue
docker
documentation
enhancement
help wanted
needs information
pull-request
question
stale
unfortunate
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/fake-gcs-server#124
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @chunming-c on GitHub (Mar 14, 2022).
Original GitHub issue: https://github.com/fsouza/fake-gcs-server/issues/713
Hi, thank you for the work. However, when upgrade to
v1.37.0,objectwas failed to be retrieved by gcs client. The tricky part is the object does exist and accessible bycurl.Version
@fsouza commented on GitHub (Mar 14, 2022):
Hi @chunming-c, can you share how you started the server? Like which arguments you provided to it.
@chunming-c commented on GitHub (Mar 14, 2022):
Yeah sure. The server is started by docker compose with config below
@fsouza commented on GitHub (Mar 14, 2022):
Can you try setting
-public-hosttolocalhost:4443?@nabeelz7 commented on GitHub (Mar 14, 2022):
We were also seeing similar issue as @chunming-c. Then changed our entrypoint
-public-hostvalue to the following per @fsouza tip and now it works again in v1.37 (we use 80/http instead of 4443/https):Is this worth an update to README.md @fsouza ?
@chunming-c commented on GitHub (Mar 15, 2022):
Yup it works after change, thanks! But what change caused the issue?
@miklosboros commented on GitHub (Mar 25, 2022):
We had the same issue and I have tracked down the possible change that introduced it. Please, refer to my note at this pull request: PR comment