Best Practices for Docker files

Open
#665 0 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

No Dockerfile, test, or entry point is named. Start by locating the Docker image build definitions used by the Splunk Operator for Kubernetes and reviewing how the Splunk Enterprise images handle filesystem writes; done means the relevant images apply the requested container security practices without breaking installation.

Written by the indexing model from the issue text.

Description

The docker image needs to apply best security practices for container such as a read-only root file system. This is an issue when the Splunk Operator for Kubernetes install Splunk enterprise images that have write permissions on the root filesystem and large corporations who scan for such vulnerabilities starts throwing alarms on the Splunk cluster.

Dominant language
Python
Stars
549
Forks
277
Avg merge
3d 9h
Merged PRs (30d)
2

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.

More from splunk/docker-splunk

All issues in splunk/docker-splunk

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.