Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. GitLab
  3. How to run a GitLab container registry (2024)

How to run a GitLab container registry (2024)

Scheduled Pinned Locked Moved GitLab
3 Posts 2 Posters 334 Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • D Offline
    D Offline
    djxx
    wrote on last edited by
    #1

    I can see some old posts from 2022 that have some complicated steps to install the Docker Registry app and link GitLab to it. Is it possible to use the built-in registry by making the configuration edits here?

    https://docs.gitlab.com/ee/administration/packages/container_registry.html?tab=Self-compiled+(source)

    It seems it would just need another open port, but as I understand Cloudron apps have to pre-define the ports they're allowed to listen on, so this option would need to be built into the Cloudron app definition and I don't see it anywhere.

    I'd much rather use this "set and forget" container registry approach, since it makes it easier to connect to other parts of GitLab.

    1 Reply Last reply
    1
    • D Offline
      D Offline
      djxx
      wrote on last edited by djxx
      #2

      I couldn't find a good way to do it just with GitLab so I went ahead and installed another app. I'd still like to hear if this is possible with GitLab alone.

      Overall, it took about 10 minutes to set it up this way, which is better than not having repository functionality. One note is that the way the docker registry app identifies itself, the port is VERY important in how you login. Previously I was able to auth with my GitLab hosted docker repository with a URL like:
      docker login registry.mydomain.com

      but this didn't work at all with the Cloudron Docker Registry hosted at the same domain. I had to change to:
      docker login registry.mydomain.com:443

      yes - the port is apparently important!

      1 Reply Last reply
      1
      • jamesJ Offline
        jamesJ Offline
        james
        Staff
        wrote last edited by
        #3

        Hey @djxx I made this topic into a normal topic for now since this seems more like a discussion than an issue that can be marked as solved.
        I hope you find this agreeable and if not, feel free to comment and mark this topic as a question again.

        1 Reply Last reply
        0
        • jamesJ james marked this topic as a regular topic
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • Bookmarks
        • Search