SeleniumHQ / SeleniumHQ/docker-selenium

[🚀 Feature]: Transparency on files written inside the docker containers

Open
#2,382 12 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

needs-triaging
Dominant language
Go
Stars
8.7k
Forks
2.5k
Avg merge
10h 16m
Merged PRs (30d)
20

Description

Feature and motivation

My organization is preventing spinning up containers without understanding where the files are written in the containers. Can we pls document all the files written inside the containers such that we can mount those folders where the files are written. I would recommend writing files only in the temp directory and not anywhere else to have a secured selenium HQ containers running.

Usage example

example: https://github.com/SeleniumHQ/docker-selenium/blob/trunk/NodeChromium/Dockerfile
When container is spin up, if there any files needs to be written by the jar or services, we need to write all the files only in /tmp folder and avoid writing any files after spin up inside the root folders including opt/bin/ etc..

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with NodeChromium/Dockerfile and trace the JAR and services it starts to identify files written after container startup. Document each written path and indicate which paths can be mounted or moved to /tmp; done means the container file-write locations and the requested storage guidance are documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker
Domain
documentation, infrastructure
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.