Skip to content
This repository was archived by the owner on Mar 10, 2023. It is now read-only.
This repository was archived by the owner on Mar 10, 2023. It is now read-only.

[Feature request] Support GitLab container registry #698

@khos2ow

Description

@khos2ow

Current Behaviour

Currently there's no way to use GitLab container registry as part of the deployment, the reason is URLs of the registry are slightly different than the ones available in other registries (e.g. DockerHub).

  • GitLab: https://registry.example.com/group/project:tag
  • GitLab: https://registry.example.com/group/project/image:tag (extra /<foo> is valid in gitlab, up to three level deep)
  • DockerHub: group/project:tag (simplified for the sake of writing here)

The relevant part of the code is here:

if sharedRepo {
imageRef = registry[:len(registry)-1] + "/" + owner + "-" + repo + "-" + imageName
} else {
imageRef = registry + "/" + owner + "/" + repo + "-" + imageName
}

Note that imageName is being appended to repo by a -, which breaks gitlab registry. Considering the project exists at https://git.example.com/group/project:

  • Invalid: https://registry.example.com/group/project-latest-master-<sha>
  • Valid: https://registry.example.com/group/project:latest-master-<sha>
  • Valid: https://registry.example.com/group/project/fn-name:latest-master-<sha>

On the same topic and slightly different issue (let me know if you'd like me to open another issue for this), owner in the code above (line 205 and 207) in GitLab depends on the profile. Considering user name of khos2ow and full profile name of Khosrow Moossavi, owner will be set to full profile name which breaks the URL format. Considering the project exists at https://git.example.com/khos2ow/project:

  • Invalid: https://registry.example.com/Khosrow Moossavi/project:latest-master-<sha>
  • Expected: https://registry.example.com/khos2ow/project:latest-master-<sha>

Possible Solution

  • First issue: Intelligently choose / over - when building image only for GitLab container registry.
  • Second issue: haven't investigated further to see what would be available

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions