Could not chown /vault/config (may not have appropriate permissions) about vault-helm

[jasonodonnell]

Hi @laurentiuspurba!

There's an environment variable SKIP_CHOWN that should be set to true to avoid the chown code from running within the Vault container. This should already be set by default, can you check if it is in the Vault pod?

[jasonodonnell]

Hi @laurentiuspurba, I did identify a bug with audit storage and HA mode (#75). Will fix this soon. Thanks for the report!

[laurentiuspurba]

Hi @jasonodonnell, Thanks for keeping me posted. Looking forward for the fix. Thank you.

[laurentiuspurba]

Hi @laurentiuspurba!

There's an environment variable SKIP_CHOWN that should be set to true to avoid the chown code from running within the Vault container. This should already be set by default, can you check if it is in the Vault pod?

Hi @jasonodonnell, I just wanted to give you all information that you need. I can see the enviroment variable SKIP_CHOWN was set to true.

[jasonodonnell]

@laurentiuspurba I just noticed the problem you're encountering from the logs you provided:

You are using a very old version of Vault and this is why you're seeing chown errors (SKIP_SETCAP didn't exist at that time):

Version: Vault v1.0.3

Can you upgrade to the newest image: vault:1.2.3? Please check your container repository where the image is being persisted. It's possible that an old image was tagged with a new version.

[laurentiuspurba]

@jasonodonnell, sure, I will try vault1.2.3. Thanks!

[laurentiuspurba]

Hi @jasonodonnell After using Vault v1.2.3, I don't see any warning related to chown. Let me know if I should close this issue. Thank you.

[jasonodonnell]

Great, closing!