# flyctl for GitLab CI (using official docker image)

**URL:** <https://community.fly.io/t/flyctl-for-gitlab-ci-using-official-docker-image/22394>\
**Category:** General\
**Tags:** wishlist, dev, flyctl, login-only\
**Created:** [October 22, 2024, 10:39pm UTC](https://community.fly.io/t/flyctl-for-gitlab-ci-using-official-docker-image/22394 "2024-10-22T22:39:00Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![tmaier](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/tmaier/32/14838_2.png) [@tmaier](https://community.fly.io/u/tmaier)\
**Post date:** [October 22, 2024, 10:39pm UTC](https://community.fly.io/t/flyctl-for-gitlab-ci-using-official-docker-image/22394/1 "2024-10-22T22:39:00Z")

</div>

I wanted to use [the official docker image](https://github.com/superfly/flyctl/pkgs/container/flyctl) for GitLab CI to avoid the need to install fly manually in each job. And to reduce the number of code I need to maintain myself.

```auto
flyctl:
  image:
    name: ghcr.io/superfly/flyctl
    entrypoint: [""]
  script:
    - flyctl version

```

This does not work, since the image is based on `scratch`.  
`scratch` makes sense, if the image is used in other contexts.  
However, for GitLab CI, one needs some kind of shell.

This is why I why I request you to add an official image, ready for CI.  
This could be a simple alpine or debian based image with bash or sh installed.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/fly1/original/3X/6/e/6e8955d00cb218e186ebbe3a6ab06fefdce15290.svg) [@system](https://community.fly.io/u/system)\
**Post date:** [October 29, 2024, 10:39pm UTC](https://community.fly.io/t/flyctl-for-gitlab-ci-using-official-docker-image/22394/2 "2024-10-29T22:39:49Z")

</div>

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.