Photon's ISO and OVA images ship under a EULA while its source is GPLv2, and the newest release is from 2023
Minimal Linux container host
At a glance
- What is it?
- vmware/photon is a C-based minimal Linux container host tuned to run as a guest on VMware ESXi, distributed as ISO, OVA, and cloud images and built from a second checkout of its own common branch. Its newest release tag is three and a half years old, and its license position takes three separate documents to state.
- Who is it for?
- Photon suits someone running virtual machines specifically on VMware infrastructure, where a kernel tuned for ESXi is the reason to use it rather than a general-purpose minimal distribution. Three things to know first.
- Can I use it commercially?
- Check first. The repository uses a licence we do not classify automatically, so read its LICENSE file before any commercial use.
- Is it still maintained?
- Yes. The repository received new commits within the last day.
- What is it written in?
- Mainly C, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- vmware/photon3,182 ★ · +4
| Repository | 2026-09-24 | 2026-11-15 |
|---|---|---|
| vmware/photon | 3.2k | 3.2k |
4 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The images are under a EULA and the source is under GPLv2
The license section takes two sentences and three documents, and the split is the kind worth reading twice.
The first sentence covers the artefacts you actually install. The Photon OS ISO and OVA images are distributed under the Photon OS EULA.
The second covers the repository. With the exception of the libtdnf source code, Photon OS source code is distributed under GNU GPL v2. The libtdnf source code is distributed under GNU LGPL v2.1.
So the binary you flash to a hypervisor is under a vendor EULA, the source is copyleft, and one component is under a weaker copyleft with linking exceptions. That combination is coherent for an operating system that ships as a product, and it means the word open source in the project description applies to the source rather than to the image.
A third document is referenced for the detail, the Photon OS Open Source License file.
No license is recorded for the project as a whole, which is consistent with a project that does not fit a single identifier.
If your use is running the ISO as a guest, the EULA is the document that applies. If your use is reading, building, or redistributing the source, it is the GPLv2 and the LGPLv2.1.
Five license and notice files sit in the root for three stated licenses
The top-level listing carries more licensing files than any other kind of file, and counting them is instructive.
There is a `COPYING` file, which is the conventional name for a copyleft license text. There is an `EULA.txt`. There is a `LICENSE.md`, which the README points at for the open source license details. And there are two notice files, `NOTICE-Apachev2` and `NOTICE-GPL2.0`.
That is five documents. The README's license section names three licenses: the EULA for the images, GPLv2 for the source, and LGPLv2.1 for libtdnf.
So there is a notice for Apache 2.0 in the tree, and no Apache 2.0 license mentioned anywhere in the license section. Either a bundled component carries an Apache license that the summary paragraph does not cover, or the notice is inherited from something the project no longer ships. There is also no `NOTICE-LGPL` for the one component the prose singles out.
This is what a project looks like after a decade of accumulating dependencies under different terms, with the front page reduced to the three that matter most.
Alongside the license files there is a `CREDITS` file and a `CHANGELOG.md`, plus a `SPECS/` directory in capitals and a `support/` directory.
The newest release is from April 2023 and the branch has been pushed since
The three most recent releases are 5.0-GA from 2023-04-28, 5.0-RC from 2023-03-31, and 5.0-Beta from 2023-01-30.
The default branch is `5.0`, and the last push to it was on 2026-10-01. So the branch has been receiving commits for three and a half years after the last tag on it.
The tag naming is also its own convention. There is no `v` prefix, and the three tags use two different spellings for the same idea, `GA` in uppercase and `Beta` with only a capital B.
And the README still opens its download section with a heading announcing that Photon OS 5.0 GA is here. That release is three and a half years old.
None of this means the branch is dead. A security-patched operating system gets kernel and package commits long after a feature release, and a system whose value is being current on kernel fixes is exactly the case where the branch matters more than the tag.
It does mean a version number is a poor way to describe what you are running. The security advisories page is linked separately from the download guide for that reason, and it is the page to read for a deployment that matters.
The 5.0 content itself is listed further down, and it reads like a feature release rather than a patch train.
Building requires cloning the same repository twice, on two branches
The build section opens with a requirement that no other minimal distribution asks for.
It says Photon OS 5 now requires the `common` branch as part of the build system, and that to build Photon 5 you need to clone the `common` branch alongside the Photon 5.0 release branch and provide its path during the build.
The two commands are:
git clone https://github.com/vmware/photon.gitand then
git clone -b common https://github.com/vmware/photon.git commonRun both clone commands from the same parent directory: the release checkout and the `common` checkout then sit side by side. Enter the Photon checkout before running `make`.
The second clone supplies build tooling; from the Photon checkout, `../common` refers to its sibling directory.
The path can be given two ways. Either edit or create `build-config.json` in the photon directory:
{
"common-branch-path": "../common"
}or pass it on the command line when invoking the build:
make package COMMON_BRANCH_PATH="../common"So the build toolchain lives in a second checkout of the same project, side by side with the release branch it builds.
The build hard-fails at parse time without jq and reads two config keys when one is documented
The build file is short and one detail in it will stop a first build immediately.
It declares a single tool in its tools list, which is `jq`, and then it checks for it during parsing rather than during the build. If the command is not found, the file raises an error saying the tool is not installed and asking that it be installed to proceed.
That is an early and friendly failure. It also means the build refuses to start on a machine with the compiler toolchain and no JSON reader, which is not an obvious combination.
From that file, the build reads configuration with jq in two places. One line pulls the `common-branch-path` key and assigns it, which is the path the README documents. A second line pulls a different key, `stage-path`, resolves it to an absolute path, and assigns that.
So the configuration file carries at least two keys and the README describes only one of them. A first-time builder following the documentation creates a file with one key and then meets a build that reads another.
Two more details are worth noting because they explain how the build tracks state. A first-pass marker file is placed in `/tmp`, and its name is derived from the absolute path of the build directory with every slash replaced by a dash. Two checkouts in different directories therefore get different markers, and the same checkout reuses one.
The file also removes that marker as it is parsed, before any target runs.
Any target name becomes an argument to build.py and clean is matched as a prefix
The build file has two targets, and the second one is a pattern rule that matches everything.
The named target is `all`, which is also the default goal. It reads two variables to decide what to do: if a package list is set it passes that list through, otherwise it checks whether a variable asks for the extra package set, and failing both it falls through to the ordinary package set.
The pattern rule is a single percent sign. Whatever you type after `make` is passed as an argument to the build script's target option. There is no list of valid targets, so an invalid name is not rejected at that point; it becomes a target name handed to the script.
That pattern rule also carries the state logic. After the build script runs, the rule touches the first-pass marker, but it explicitly skips that when the target name starts with `clean`.
The test is a prefix match on the string rather than a comparison against a list of cleaning targets. So any name beginning with those five characters takes the cleaning branch, and a target whose name begins with those characters but is not a cleaning target will not mark the pass as complete.
It is a small thing, and it is the kind of detail that only surfaces for someone building with an unusual target name.
The contributing link points at master and the maintainers link at dev
The contributing section links three documents and two of them are on branches other than the default.
The default branch of this repository is `5.0`. The contributing guidelines link resolves to a file on the `master` branch, and the maintainers link resolves to the authors file on the `dev` branch.
So the front page of the release branch sends contributors to read guidance from two other lines. That is not necessarily wrong, since a project can keep its contribution guide and its author list on a development branch deliberately, but it means the guidance a contributor reads is not maintained alongside the code it applies to.
The process itself is a Contributor License Agreement, and it is enforced by a bot. If you have not signed the CLA, the bot walks you through the process and updates the issue when you open a pull request. There is a separate FAQ for the agreement and a route to the issue tracker for questions.
The project also asks contributors to discuss plans before writing code, through a GitHub issue or with the maintainers named in that authors file, via a Slack channel, and gives the reason: so other contributors can point them in the right direction, give feedback on the design, and find out whether someone else is already working on the same thing.
That is a well-stated process for a project of this size. A CLA rather than a Developer Certificate of Origin is the notable choice, since it means a signed agreement is retained rather than a per-commit sign-off.
ARM64 is specified on the ESXi kernel and Mesos is still named as an orchestrator
Two details in the feature description are worth pulling out, because they are both narrower than they first read.
The first is processor support. The 5.0 feature list names ARM64 on the Linux-esx kernel, but that statement alone does not establish whether other ARM64 deployment options are supported; consult the platform-specific documentation.
That is consistent with the first of the four highlights, which says the Linux kernel is tuned for performance when Photon OS runs on VMware ESXi. This is an operating system built to be a guest, and the ARM64 statement belongs to that same frame.
The second is orchestration support. The container highlight says Photon OS includes the Docker daemon and works with container orchestration frameworks such as Mesos and Kubernetes.
Both of those statements date from a period when the container ecosystem on Linux ran through the Docker daemon and when Mesos was a live orchestrator. The rest of the same feature list is more current: control group v2, XFS and BTRFS, a real-time kernel option, a container builder tool, and a container runtime security component.
So the distribution is being maintained, and the parts of the description that were written about the older container stack are the parts that have not been revisited. That is worth knowing when you read the highlights as a current summary rather than as a description.
Editorial conclusion
Photon suits someone running virtual machines specifically on VMware infrastructure, where a kernel tuned for ESXi is the reason to use it rather than a general-purpose minimal distribution. Three things to know first. The licensing is split three ways, with the images under a proprietary EULA, most of the source under GPLv2, and one component under LGPLv2.1, so read which of the three your use falls under. The newest release tag is from April 2023 even though the branch is still being pushed, so a version number tells you less than the branch does. And building requires a second clone of the same repository on a different branch, which is not a step any other minimal distribution asks for.
Frequently asked questions
What is Photon OS and what is it optimised for?
Photon OS is an open source minimal Linux container host written in C, optimised for cloud-native applications, cloud platforms, and VMware infrastructure. Its first named highlight is that the Linux kernel is tuned for performance when the system runs on VMware ESXi, and it includes the Docker daemon.
How is Photon OS licensed?
Three ways. The ISO and OVA images are distributed under the Photon OS EULA, source code is distributed under GNU GPL v2 with the exception of libtdnf, and the libtdnf source code is distributed under GNU LGPL v2.1. and no single license is recorded for the project as a whole.
What formats does Photon OS ship in?
ISO, OVA, and cloud images including an Amazon AMI, a Google Cloud GCE image, and an Azure VHD. There is also an official Vagrant box, used with vagrant init vmware/photon, plus a separate plugin repository for Photon guests. The file notes some users found the box requires VirtualBox 4.3 or later.
What do I need to build Photon OS from source?
Two clones of the same repository and a JSON reader. The release branch is cloned as usual, then the common branch is cloned alongside it with git clone -b common https://github.com/vmware/photon.git common. The path is given either through a common-branch-path key in build-config.json or as a make argument. The build file also fails immediately if jq is not installed.
What is the latest Photon OS release?
5.0-GA, published on 2023-04-28, preceded by 5.0-RC in March 2023 and 5.0-Beta in January 2023. The default branch is 5.0 and its last push was on 2026-10-01, so the branch carries three and a half years of commits above the last tag.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/vmware-photon)Star history chart for your README
[](https://hysenlabs.com/projects/vmware-photon)Was this useful?