Tecnativa / Tecnativa/docker-socket-proxy
Can't run as read_only any more
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.8k
- Forks
- 207
- PR merge metrics
- No merged PRs in 30d
Description
Hi i try to run all my containers if possible in read_only mode, but since the 0.1.2 version the container needs to generate the file /usr/local/etc/haproxy/haproxy.cfg but as the directory /usr/local/etc/haproxy/ contains the template file i can't mark it as tmpfs..
Is there some way to change where the generated file is stored?
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 locating where /usr/local/etc/haproxy/haproxy.cfg is generated and how the existing template in /usr/local/etc/haproxy/ is used. Check the container configuration and related documentation; the work is done when read_only containers can place the generated configuration in a writable location without overwriting or requiring the template directory as tmpfs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100