Open emperorkebab opened 3 months ago
Hi @emperorkebab, please add branch-* labels to identify which branch(es) this C-bug affects.
:owl: Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.
Hello, I am Blathers. I am here to help you get the issue triaged.
Hoot - a bug! Though bugs are the bane of my existence, rest assured the wretched thing will get the best of care here.
I have CC'd a few people who may be able to assist you:
If we have not gotten back to your issue within a few business days, you can try the following:
:owl: Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.
I just realized this could made irrelevant by https://github.com/cockroachdb/cockroach/pull/85062 if it gets merged
Describe the problem
When running crdb docker container with the option
user: 1000:1000
the container fails with the following log error:which i think originates from here: https://github.com/cockroachdb/cockroach/blob/6d362070be19565f0252af57296dfe8e8bbb8365/build/deploy/cockroach.sh#L134
To Reproduce
mycrdb/certs
andmycrdb/data
(owned by user 1000, and default perms 755) to avoid "could not write CAs" cockroach error when initializing.Expected behavior
The cockroachdb container gets generated without errors, and the generated content in the bind volumes are owned by the user with id 1000 instead of root.
Additional data / screenshots
Related to:
Environment:
Additional context What was the impact? Can't proceed with container hardening.
Jira issue: CRDB-39655