[GH-ISSUE #51] DockerHub Image Causes Exception #2162

New issue

Closed

opened 2026-03-15 17:48:58 +03:00 by kerem · 3 comments

kerem commented

2026-03-15 17:48:58 +03:00

Owner

Originally created by @MarcvanMelle on GitHub (Jul 22, 2019).
Original GitHub issue: https://github.com/fsouza/fake-gcs-server/issues/51

Originally assigned to: @fsouza on GitHub.

From scratch pulling fsouza/fake-gcs-server causes an exception in standard_init_linux.go

$ docker run --name fake-gcs-server -p 4443:4443 fsouza/fake-gcs-server
$ Unable to find image 'fsouza/fake-gcs-server:latest' locally
$ latest: Pulling from fsouza/fake-gcs-server
$ 050382585609: Pull complete
$ ac2a410f0388: Pull complete
$ Digest: sha256:a3364067c3887a157cf16b0f91a0c7412393a0c5183cf396c220a2b9e2755dd4
$ Status: Downloaded newer image for fsouza/fake-gcs-server:latest
$ standard_init_linux.go:211: exec user process caused "no such file or directory"

However, building the image from the repo and running the same is successful.

$ docker run --name fake-gcs-server -p 4443:4443 fsouza/fake-gcs-server
$ time="2019-07-22T15:17:21Z" level=info msg="couldn't load any objects from \"/data\", starting empty"
$ time="2019-07-22T15:17:21Z" level=info msg="server started at https://[::]:4443"

Originally created by @MarcvanMelle on GitHub (Jul 22, 2019). Original GitHub issue: https://github.com/fsouza/fake-gcs-server/issues/51 Originally assigned to: @fsouza on GitHub. From scratch pulling `fsouza/fake-gcs-server` causes an exception in `standard_init_linux.go` ``` $ docker run --name fake-gcs-server -p 4443:4443 fsouza/fake-gcs-server $ Unable to find image 'fsouza/fake-gcs-server:latest' locally $ latest: Pulling from fsouza/fake-gcs-server $ 050382585609: Pull complete $ ac2a410f0388: Pull complete $ Digest: sha256:a3364067c3887a157cf16b0f91a0c7412393a0c5183cf396c220a2b9e2755dd4 $ Status: Downloaded newer image for fsouza/fake-gcs-server:latest $ standard_init_linux.go:211: exec user process caused "no such file or directory" ``` However, building the image from the repo and running the same is successful. ``` $ docker run --name fake-gcs-server -p 4443:4443 fsouza/fake-gcs-server $ time="2019-07-22T15:17:21Z" level=info msg="couldn't load any objects from \"/data\", starting empty" $ time="2019-07-22T15:17:21Z" level=info msg="server started at https://[::]:4443" ```

kerem closed this issue

2026-03-15 17:49:03 +03:00

kerem commented

2026-03-15 17:49:09 +03:00

Author

Owner

@fsouza commented on GitHub (Jul 22, 2019):

Hi @MarcvanMelle. Thanks for reporting and sorry about that. I'm pushing the fix right now.

@fsouza commented on GitHub (Jul 22, 2019): Hi @MarcvanMelle. Thanks for reporting and sorry about that. I'm pushing the fix right now.

kerem commented

2026-03-15 17:49:14 +03:00

Author

Owner

@fsouza commented on GitHub (Jul 22, 2019):

This should be fixed now:

>>| docker pull fsouza/fake-gcs-server
Using default tag: latest
latest: Pulling from fsouza/fake-gcs-server
050382585609: Already exists
59b0b2068f9e: Pull complete
Digest: sha256:de859a113efc00fc72e32d6b08298df3d2e0d589143b48f4a0204b05eab07662
Status: Downloaded newer image for fsouza/fake-gcs-server:latest
>>| docker run fsouza/fake-gcs-server
time="2019-07-22T15:29:36Z" level=info msg="couldn't load any objects from \"/data\", starting empty"
time="2019-07-22T15:29:36Z" level=info msg="server started at https://[::]:4443"

Also tagged 1.10.1.

Thanks for reporting and sorry about the disruption.

@fsouza commented on GitHub (Jul 22, 2019): This should be fixed now: ``` >>| docker pull fsouza/fake-gcs-server Using default tag: latest latest: Pulling from fsouza/fake-gcs-server 050382585609: Already exists 59b0b2068f9e: Pull complete Digest: sha256:de859a113efc00fc72e32d6b08298df3d2e0d589143b48f4a0204b05eab07662 Status: Downloaded newer image for fsouza/fake-gcs-server:latest >>| docker run fsouza/fake-gcs-server time="2019-07-22T15:29:36Z" level=info msg="couldn't load any objects from \"/data\", starting empty" time="2019-07-22T15:29:36Z" level=info msg="server started at https://[::]:4443" ``` Also tagged 1.10.1. Thanks for reporting and sorry about the disruption.

kerem commented

2026-03-15 17:49:19 +03:00

Author

Owner

@MarcvanMelle commented on GitHub (Jul 23, 2019):

Awesome! Thanks for the quick fix.

@MarcvanMelle commented on GitHub (Jul 23, 2019): Awesome! Thanks for the quick fix.