Skip to content

Transition to using Hubs Foundation Docker images in Community Edition #396

Open

Description

@Exairnous

In order to benefit from further development, the Community Edition deployment scripts should be updated to use the Docker images built by the Hubs Foundation instead of the archived Mozilla Docker images.

Note: before a Community Edition service that the Hubs Foundation maintains can be transitioned, its corresponding repository must have been updated to produce Hubs Foundation Docker images. See Hubs-Foundation/.github#9 for which repositories have been updated to produce Hubs Foundation Docker images.

Updates to community-edition/input-values.yaml

Overrides

Initially, the way to use the Hubs Foundation images is to add them as overrides of the Mozilla images.

Note: the override images should use the Docker Hub path with $Container_Tag as the tag, e.g. "hubsfoundation/hubs:$Container_Tag"

Final transition

Once all the overrides have been applied, the Container_Dockerhub_Username can be changed from "mozillareality" to "hubsfoundation" and the overrides can be reset back to "No".

  • Container_Dockerhub_Username and overrides reset
    • PR:

Updates to community-edition/ssl_script/cbb.yam

  • Pod > certbotbot-http > spec > image
    • This should be updated to use the Docker Hub path for the Hubs Foundation's certbotbot image with the stable-latest tag.
    • PR:

Historical notes

2026-05-12: It was originally planned that the postgrest, postgres, and haproxy services would reference the non-customized 3rd-party Docker images directly as overrides; however, it was decided at the 2026-04-21 Hubs Dev Meetup that it would be a better user experience to build Hubs Foundation Docker images of the non-customized 3rd-party services so that they can be updated at any time without requiring a release/update of the Community Edition deployment scripts.

Activity

  1. added
    Tracking IssueLabel for issues that are used as a central place to coordinate larger pieces of work
    on Mar 25, 2026
  2. changed the title [-]Transition to using Hubs Foundation and 3rd-party Docker images in Community Edtion[/-] [+]Transition to using Hubs Foundation and 3rd-party Docker images in Community Edition[/+] on Apr 7, 2026
  3. changed the title [-]Transition to using Hubs Foundation and 3rd-party Docker images in Community Edition[/-] [+]Transition to using Hubs Foundation Docker images in Community Edition[/+] on May 12, 2026
  4. Exairnous commented on May 12, 2026

    @Exairnous
    MemberAuthor

    I have updated this to reflect the revision to the plan for non-customized 3rd party services that was decided at the 2026-04-21 Hubs Dev Meetup.

  5. added
    Roadmap: ProgrammingIndicates that this issue/pull request is on the Programming Team roadmap
    on May 15, 2026
  6. Exairnous commented on Oct 8, 2026

    @Exairnous
    MemberAuthor

    Updated the tracking issue description to include Speelycaptor.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Roadmap: ProgrammingIndicates that this issue/pull request is on the Programming Team roadmapTracking IssueLabel for issues that are used as a central place to coordinate larger pieces of work

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions