The home of quay.io/gitpod-workspace-images/*/docker.cloudsmith.io/~gitpodify/gitpodified-workspace-images/* Docker images, maintained by @ajhalili2006 from @RecapTime. Merge requests are very welcome, through please take them all to upstream
gitpod-io/workspace-images repository on GitHub so we can rebase-then-merge them into here.
NOTE TO USERS/CONTRIBUTORS: CI will be temporarily broken until the Dazzle v2 migration is finshed, so the ETA is maybe between Feb. 16 and March 2, Philippine Standard Time. There is some progress on our Dazzle migration right now, but we'll still fixing the kinks and the edges on the build systems.
The official canonical repo is on GitLab SaaS at https://gitlab.com/gitpodify/gitpodified-workspace-images while keeping the GitHub copy associated with the parent repo and in sync.
Builds are always happens automagically on Red Hat Quay Container Registry from the recaptime-dev-mainline branch as we merge changes from the upstream. Click on an image name to get all available tags.
More images will be become available in the future, but you can build the images yourself if needed.
- Comes Zsh as default shell with OhMyZsh preloaded.
- UUID-related packages are included, plus ShellCheck, Hadolint and even Doppler CLI.
- We don't forget GitHub CLI and GLab CLI if you prefer not to use the VSC extensions.
ProvidedCurrently unsupported by current Dazzle setup, tracked at TBDGITPODIFY_*variables to help in community support and debugging purposes. (docker inspectour built images fordev.gitpodify.*labels)- Drop in user customizations to
~/.gitpodify/custom-zshrc.d(don't forget to exportSOURCED_VIA_CUSTOM_ZSHRCto any value to ensure your OMZ customizations were not overrided by the defaults after doing the init yourself). - Coming soon: Weekly rebuilds through GitHub Actions cronjobs to keep things fresh as possible.
While Dazzle can help us in handling image caching, we want to ensure everything is fresh as possible and to keep the vulnerability count as low as possible in Quay image scans atleast for system packages
so we choose plain .docker build built-in at Red Hat Quay Container Registry
We initially use these images we built as drop-in replacement for the upstream images built through Dazzle, but sometimes outdated cache can cause different pain points for us.
- In your
.gitpod.ymlfile: Just setimagekey to whatever the image that fits your case.
image: quay.io/gitpodified-workspace-images/full- On your custom workspace image Dockerfile: Swap
gitpod/workspace-<type>toquay.io/gitpodified-workspace-images/<type>as your base images.
# Tip: Ignore DL3007 if using Hadolint since this is harmless, unless you want to lock version with
# dazzle-build-<timestamp> tags
FROM quay.io/gitpodified-workspace-images/full:latest
# If you use base as the starting point, then change repository to this:
FROM quay.io/gitpodified-workspace-images/base:latest- With Gitpodify CLI Alpha: Run
gitpodify switch-ws-image quay.io/gitpodified-workspace-images/<type>if you set it via the.gitpod.ymlway. Otherwise, see previous method.1
Build metadata is stored in ~/.gitpodify/ws-image-metadata, so you can copy its contents via cat so we can help debug issue faster.
We want to also support RHEL and Alpine in the future, but that would be an additional workload for the maintainers, which is currently one man, so sorry.
Mostly because of the default storage limits. Technically, @ajhalili2006 also can't afford paying a few bucks (hundreds to thousands of PHP when converted).
We avoided Docker Hub as much as possible so you don't worry about pull limits on per-IP address or per-user basis.
We're currently slowly migrating to Dazzle v2 right now. Metadata stuff will then be added next very soon. We're done migrating to Dazzle v2, so we'll start synchorizing our fork against the upstream to keep things up-to-date as much as possible.
Footnotes
-
The Gitpodify CLI is under prototype status and may be go into beta state within months. If you are curious, see https://gitlab.com/gitpodify/gitpodify ↩