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
  • Brite
  • 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

Offical apps | Community apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Feature Requests
  3. Official App Store updates fail when a private registry hostname contains .docker

Official App Store updates fail when a private registry hostname contains .docker

Scheduled Pinned Locked Moved Feature Requests
2 Posts 2 Posters 110 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.
  • andreasduerenA
    andreasduerenA
    andreasdueren
    App Dev
    wrote last edited by
    #1

    Cloudron appears to match my private registry against Docker Hub because both hostnames contain .docker., selecting the private registry’s credentials for public image pulls.

    For example, the failed Matomo update logged:

    docker: pullImage: will pull registry.docker.com/cloudron/org.piwik.cloudronapp:202609212321130000. auth: yes
    

    The pull failed, followed by a Quay fallback that returned manifest unknown. Existing apps continued running, but their updates remained in an error state.

    Temporarily moving the registry to registry-docker.tld.com and updating its configured address, without changing credentials, changed the same Docker Hub pull to auth: no. All 20 pending official updates then succeeded.

    The registry-matching code in src/docker.js appears to use .includes('.docker.') to recognize Docker Hub aliases. Could this be restricted to an explicit list of Docker Hub hostnames, while requiring exact hostname matching for private registries? Private-registry credentials should not be selected for unrelated registries.

    1 Reply Last reply
    4
    • girishG
      girishG
      girish
      Staff
      wrote last edited by
      #2

      I guess we can check for .docker.com and .docker.io instead. Would that work @andreasdueren ?

      1 Reply Last reply
      2

      Hello! It looks like you're interested in this conversation, but you don't have an account yet.

      Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

      With your input, this post could be even better đź’—

      Register Login
      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