dhi.io/sorry-cypress-director
Sorry Cypress Director
Sorry Cypress director, the service that coordinates parallel Cypress test runs.
pushed 9 hours ago
linux/amd64, linux/arm64
48.84 MB
for linux/amd64
426
for linux/amd64
Active support
-
Build Level 3
Tamper-evident proof of how and from what sources this image was built. Build Level 3 is the highest the SLSA build track defines.
CycloneDX SBOM + SPDX SBOM
A software bill of materials in both CycloneDX and SPDX formats so it drops straight into your existing tooling. Audit exactly what you're shipping.
A Vulnerability Exploitability exchange document, Docker's assessment of which CVEs actually affect this image and which don't apply, so you can focus on real risk instead of chasing false positives.
Available
A link to everything used to build the image, package source code, Git repos, and build files, so you can audit or reproduce the build and stay compliant with open source licenses.
Every known vulnerability in this image, shown in full rather than hidden. The VEX data flags which ones actually apply, so you can tell real exposure from noise before you ship.
Exactly what changed in this build, down to the package bumps and fixes behind the version you're pulling.
Verifies no keys, tokens, or credentials were accidentally baked into the image.
The image layers were scanned for known malware signatures before publishing.
About Sorry Cypress Director
Sorry Cypress is an open source alternative to Cypress Cloud for running Cypress tests in parallel. The director is the service Cypress records to, and it creates the run, hands each spec file to the next free machine, collects the results and reports status to hooks such as GitHub, Slack or a webhook.
The director keeps runs in memory by default and stores them in MongoDB when the MongoDB execution driver is set, with
screenshots and videos going to S3, MinIO, Azure Blob Storage or Google Cloud Storage through a screenshots driver. This
image runs the director under Node.js and replaces agoldis/sorry-cypress-director.
About Docker Hardened Images
Docker Hardened Images are built to meet the highest security and compliance standards. They provide a trusted foundation for containerized workloads by incorporating security best practices from the start.
Why use Docker Hardened Images?
These images are published with near-zero known CVEs, include signed provenance, and come with a complete Software Bill of Materials (SBOM) and VEX metadata. They're designed to secure your software supply chain while fitting seamlessly into existing Docker workflows.
Trademarks
Sorry Cypress is distributed under the MIT License and claims no trademark of its own. This listing is prepared by Docker. All third-party product names, logos, and trademarks are the property of their respective owners and are used solely for identification. Docker claims no interest in those marks, and no affiliation, sponsorship, or endorsement is implied.