-
Notifications
You must be signed in to change notification settings - Fork 440
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
volume folder created with unexpected different user and folder #380
Comments
And one more issue/bug that I tried multiple times but the issue remains: even I've customized the $ ls -al /opt/local-path-provisioner/
total 28
drwxrwxrwx 7 root root 4096 Jan 10 04:39 .
drwxr-xr-x 4 root root 4096 Jan 10 04:38 ..
drwxrwxrwx 2 root root 4096 Jan 10 04:44 pvc-057537df-9002-4eff-a29d-ff8a52732157_xxx-clickhouse_xxx-clickhouse-log-volume-chi-clickhouse-local-0-0-0
drwxrwxrwx 4 root root 4096 Jan 10 04:44 pvc-67889c0e-a0fa-4229-9a19-941c9526812b_xxx-kafka_data-kafka-zookeeper-0 |
By adding more command in the setup: |-
#!/bin/sh
set -eu
echo mkdir -m 0777 -p "$VOL_DIR"
mkdir -m 0777 -p "$VOL_DIR"
echo chown root:root -R "$VOL_DIR"
chown root:root -R "$VOL_DIR"
echo chmod 0777 -R "$VOL_DIR"
chmod 0777 -R "$VOL_DIR"
ls -al "$VOL_DIR"
ls -al "$VOL_DIR"/../
Not sure why the folder's owner was changed from initial |
it turns out that this statement is a false alarm:
As ElasticSearch operator will try to But it's still true that volume folders may be created in the default |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
This issue was closed because it has been stalled for 5 days with no activity. |
Some volume folders created with an unexpected different user
user
, which is my current OS login user, which is NOT expected.I defined my custom config like this -- Note that I tried to tweak the
setup
script to change the owner explicitly to beroot:root
but didn't help:And the complete logs while creating the volume:
The text was updated successfully, but these errors were encountered: