Docker containers using tag v0.6.0 and v0.7.0 can not find the CLI executable

[apeteri]

I receive the following message when trying to run either of them without any arguments:

$ docker run --rm -t -i quay.io/authzed/zed # :latest, :v0.7.0 and :v0.6.0 all return the same result
exec /usr/local/bin/zed: no such file or directory

$ docker run --rm -t -i quay.io/authzed/zed:0.5.0
A client for managing Authzed from your command line.

Usage:
  zed [command]

Available Commands:
[...]

[fro-yo]

@josephschorr Running into similar issues with latest/v0.6.0/v0.7.0

$ docker run --rm -t -i quay.io/authzed/zed:v0.6.0
standard_init_linux.go:228: exec user process caused: no such file or directory

$ docker run --rm -t -i quay.io/authzed/zed:v0.7.0
standard_init_linux.go:228: exec user process caused: no such file or directory

$ docker run --rm -t -i quay.io/authzed/zed:latest
standard_init_linux.go:228: exec user process caused: no such file or directory

$ docker run --rm -t -i quay.io/authzed/zed:0.5.0

A client for managing Authzed from your command line.

Usage:
  zed [command]

Available Commands:
[...]

[josephschorr]

Need to investigate why the image is still not working, yet works when built locally