feat: readOnlyRootFilesystem can`t be used

Open
#525 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
docker, shell
Domain
infrastructure

Research direction

Start with /opt/app-root/etc/generate_container_user and the reported attempt to write /opt/app-root/etc/passwd when readOnlyRootFilesystem is enabled. Trace how these paths are assembled in the container image and determine how an emptyDir can provide the passwd contents without replacing the generator. Done means the container starts successfully with a read-only root filesystem and the requested passwd data is available.

Written by the indexing model from the issue text.

Description

Hi,

I have this issue.

I set readOnlyRootFilesystem: true

When I start the container I get:

/opt/app-root/etc/generate_container_user: line 10: /opt/app-root/etc/passwd: Read-only file system

I would like to use an empty dir to store /opt/app-root/etc/passwd contents. But this seesm not possible since /opt/app-root/etc/generate_container_user is in the same folder.

Dominant language
Shell
Stars
173
Forks
288
Avg merge
6d 1h
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

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 sclorg/s2i-nodejs-container

All issues in sclorg/s2i-nodejs-container

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.