Fly CLI does not install on devcontainer

[lukeocodes]

It would appear that whatever format the CLI used to be in, it is no longer in? gzip: stdin: not in gzip format

 => ERROR [dev_containers_target_stage 6/7] RUN --mount=type=bind,from=de  1.1s
------
 > [dev_containers_target_stage 6/7] RUN --mount=type=bind,from=dev_containers_f
eature_content_source,source=flyctl_1,target=/tmp/build-features-src/flyctl_1
  cp -ar /tmp/build-features-src/flyctl_1 /tmp/dev-container-features  && chmod
-R 0755 /tmp/dev-container-features/flyctl_1  && cd /tmp/dev-container-features/
flyctl_1  && chmod +x ./devcontainer-features-install.sh  && ./devcontainer-feat
ures-install.sh  && rm -rf /tmp/dev-container-features/flyctl_1:
0.276 ==========================================================================
=
0.276 Feature       : Fly.io CLI
0.276 Description   : Install [flyctl](https://github.com/superfly/flyctl) - Com
mand line tools for [fly.io services](https://fly.io/)
0.276 Id            : ghcr.io/dhoeric/features/flyctl
0.276 Version       : 1.0.0
0.276 Documentation : https://github.com/dhoeric/features/tree/main/src/flyctl
0.276 Options       :
0.276     VERSION="latest"
0.276 ==========================================================================
=
0.285 (*) Installing flyctl...
0.811 FLYCTL_VERSION=2023.9.8
1.062
1.062 gzip: stdin: not in gzip format
1.062 tar: Child returned status 1
1.062 tar: Error is not recoverable: exiting now
1.063 ERROR: Feature "Fly.io CLI" (ghcr.io/dhoeric/features/flyctl) failed to in
stall! Look at the documentation at https://github.com/dhoeric/features/tree/mai
n/src/flyctl for help troubleshooting this error.

WSL VSCode devcontainers, Windows 11, Node 20.13

[lukeocodes]

Confirming that it works if you manually give it a version (even the latest version), but it breaks when you default to latest. I manually gave it this week's 0.2.28 (which is pinned as latest) and it works without issue.

[GMkonan]

@lukeocodes Yeah, I've made an issue (#25) and a PR (#26) potentially fixing this, but I think this repo is not being maintained anymore, so I don't think it will get merged anytime soon. I may recreate this issue in another repo with the fix and send to devcontainers.