Jewel container image now available on GHCR

Project Discussions
,
1

Hi everyone,

Following up on the Ansible Jewel project announcement and the AWX modernization: Ansible Jewel post, one of the early pieces of feedback we heard was that building Jewel from source added friction for anyone wanting to try it out. Today we’re taking a step to address that.

A pre-built Jewel container image is now published to the GitHub Container Registry on every push to the devel branch:

docker pull ghcr.io/ansible/jewel:latest

What you get

  • Multi-architecture — linux/amd64 and linux/arm64

  • API server only — the image ships the Jewel API and proxy layer without the platform UI, keeping it lightweight and focused on what the community needs for development and testing

  • Automated — a new image is built and pushed on every merge to devel, so latest always reflects the current state of the branch

Important: this tracks devel, not a release

There are currently no versioned releases or stable tags for Jewel. The latest tag always points to the most recent devel build. Per-commit SHA tags (sha-<short> and sha-<full>) are available if you need to pin to a specific build, but these are snapshots of development, not releases.

Getting started

Pull the image:

docker pull ghcr.io/ansible/jewel:latest

Jewel requires PostgreSQL, Redis, and configuration to run, so a standalone docker run won’t work out of the box. To get a full working environment, clone the repo and use the development setup:

git clone https://github.com/ansible/jewel.git
cd jewel
make docker-compose

See the repo README for full details.

A note on the platform UI

The published image does not include the platform UI. The UI is maintained separately and is not currently available as a public image, so community builds are API-only for now.

What’s next

We’re interested in making the contributor experience better over time. Some things we’re thinking about:

  • Documentation improvements — better getting-started guides for running Jewel with other services

  • Release tagging — establishing a versioning and release cadence as the project matures

  • UI availability — exploring options for making the full stack accessible to the community

We’d like your feedback

We’re interested in all feedback, but especially:

  • How are you using (or planning to use) Jewel? Understanding your use cases helps us prioritize.

  • What’s still missing to get started? If you’ve tried running Jewel and hit a wall, we want to know about it.

  • Ideas on what a release cadence could look like — what would be most useful for your workflow?

Feel free to reply here or open an issue on the repo.

Links

3 Likes
2

So many things in relation to this post. That again are not a step in the right direction. Oh and before you say it’s a required step for releases. I say poppy-cock.

why? please follow the chain yourself, starts here → AWX modernization: Moving forward - #39 by jon-nfc

If red hat wants open source community developers to contribute. red hat can make the product usable for open source community members who are not developers. That means nothing less than releases, like any other software product. That includes everything to make it work. PERIOD.

Yeah lets raise an issue. Just so it can never be triaged, let alone worked on. Here’s one for ya [Feature]: Official builds and documentation · Issue #76 · ansible/jewel · GitHub. want more examples go to any ansible repo and look for yourself.