[
https://issues.apache.org/jira/browse/SPARK-43368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yikun Jiang resolved SPARK-43368.
---------------------------------
Fix Version/s: 3.5.0
Resolution: Fixed
Issue resolved by pull request 45
[https://github.com/apache/spark-docker/pull/45]
> Address DOI comments about /etc/passwd
> --------------------------------------
>
> Key: SPARK-43368
> URL: https://issues.apache.org/jira/browse/SPARK-43368
> Project: Spark
> Issue Type: Sub-task
> Components: Spark Docker
> Affects Versions: 3.5.0
> Reporter: Yikun Jiang
> Assignee: Yikun Jiang
> Priority: Minor
> Fix For: 3.5.0
>
>
> chgrp root /etc/passwd && chmod ug+rw /etc/passwd
> Wider permissions on /etc/passwd is concerning. What use case is broken if
> the running user id doesn't exist?
> echo ... >> /etc/passwd
> Having the entrypoint itself modify /etc/passwd is fragile. Are there
> features that are broken if the user doesn't exist in /etc/passwd (like
> PostgreSQL's initdb that refuses to run)? Minimally, this should probably use
> useradd and usermod rather than hand editing.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
