SeleniumHQ / SeleniumHQ/docker-selenium
[🚀 Feature]: Migrate to S6 overlay from Supervisord
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8.7k
- Forks
- 2.5k
- Avg merge
- 10h 16m
- Merged PRs (30d)
- 20
Description
Feature and motivation
Following few articles
S6-overlay is a container-focused process manager that offers end-to-end management of the container's lifecycle, from initialization to graceful shutdown. Its innovative design and feature set make it a compelling alternative to other process managers, such as supervisors
- https://github.com/just-containers/s6-overlay
- https://ahmet.im/blog/minimal-init-process-for-containers/
- https://platformengineers.io/blog/s6-overlay-quickstart/
Evaluate the pros and bring S6 overlay to current containers.
Usage example
Changes in container's processes in background, there is no impact for end-user experience
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by reviewing how the current containers use Supervisord and compare that lifecycle with the referenced S6-overlay documentation. Done means evaluating the trade-offs, migrating the current containers, and confirming background process changes do not affect end-user experience.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100