Skip to content

Issue with release-cli:latest image on self hosted "invalid hostname"

I am using the default release cli image inside my job:

stages:
  - release

create-release:
  stage: release
  image: registry.gitlab.com/gitlab-org/release-cli:latest
  script: echo "Creating release $CI_COMMIT_TAG"
  rules:
    - if: $CI_COMMIT_TAG
  release:
    tag_name: $CI_COMMIT_TAG
    description: "Release $CI_COMMIT_TAG of components in $CI_PROJECT_PATH"

Which seeming has been failing when trying to push releases of my project on our self hosted GitLab Enterprise Edition v18.1.4-ee. Our domain is a context within a bigger URL.

I believe this is more directly related to glab cli causing some type of issue but I am not seeing any related issues within the gitlab cli issues.

Created fresh repository.
Checking out 51cedea4 as detached HEAD (ref is 1.0.1)...
Skipping Git submodules setup
Executing "step_script" stage of the job script 00:00
$ echo "Creating release $CI_COMMIT_TAG"
Creating release 1.0.1
Executing "step_release" stage of the job script 00:01
$ if command -v glab &> /dev/null; then # collapsed multi-line command
A new version of glab has been released: v1.58.0 -> v1.68.0
https://gitlab.com/gitlab-org/cli/-/releases/v1.68.0
ERROR: error parsing '--hostname': invalid hostname "internal.hostname.com/gitlab-licensed"
Try 'glab auth login --help' for more information.
Cleaning up project directory and file based variables 00:01
ERROR: Job failed: command terminated with exit code 1

Is there something I am doing wrong here? I am unable to figure out what to do through looking through related issues in the past.