PrestaShop / PrestaShop/docker
Run image with a random user and readOnly root filesystem
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 281
- Forks
- 190
- PR merge metrics
- No merged PRs in 30d
Description
I want to run a Prestashop on a secured Kubernetes clusters with some constraints :
- Random user id
- No capabilities
- Readonly filesystem
I was able to change the default listening ports, by using Configmap to overrides "ports.conf".
But I've got a problem trying to put emptyDir where apache must write logs and lock file, because it needs to write in "/tmp".
But if I add an emptyDir on "/tmp", I love all scripts.
Is these possible to think about :
- Use environment variable to configure listening port of apache
- Put all scripts in another folder than "/tmp" ? (but continue to use "/tmp" for any writing operations)
Contributor guide
No contributing guide indexed for this repository
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
Start by inspecting the image's Apache configuration, especially ports.conf, and the scripts that are placed under /tmp. Check how Apache logs, lock files, and other writes are configured under a random user and read-only root filesystem. Done means the requested port configuration and script placement work without losing scripts or requiring capabilities.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- apache, docker, kubernetes
- Domain
- devops, infrastructure, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100