docker-entrypoint-initdb.d scripts don't run unless COCKROACH_USER is set

[brianvans]

Describe the problem

We rely on the /docker-entrypoint-initdb.d directory to run a script to initialize some databases, and we've run into some inconsistent behavior with start-single-node wherein the scripts under that directory don't get run if COCKROACH_USER isn't set. It seems like it's because the entrypoint is opening an interactive cockroach sql session which blocks execution of the scripts under /docker-entrypoint-initdb.d.

I'm wondering if opening an interactive cockroach sql session is intended behavior, or an unintentional result of calling run_sql_query without any query arguments here.

To Reproduce

echo 'CREATE DATABASE IF NOT EXISTS "hello_world";' > init-db.sql
docker run \
  -ti \
  --rm \
  -v $PWD/init-db.sql:/docker-entrypoint-initdb.d/init-db.sql \
  -p 26257:26257 \
  cockroachdb/cockroach:v23.1.10 \
  start-single-node --insecure

Expected behavior

A single node instance is started up and the "hello_world" database exists.

Jira issue: CRDB-31707

[blathers-crl]

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 was unable to automatically find someone to ping.

If we have not gotten back to your issue within a few business days, you can try the following:

• Join our community slack channel and ask on #cockroachdb.
• Try find someone from here if you know they worked closely on the area and CC them.

_{🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.}

[jlinder]

This doesn't look like a dev inf issue. It seems like it's a best fit for sql foundations. If that doesn't seem right, please check in with Ken.

[rafiss]

Thanks for the report @brianvans. Is this blocking you from doing anything, or do you have a workaround?

[brianvans]

Thanks for the report @brianvans. Is this blocking you from doing anything, or do you have a workaround?

We worked around it by setting COCKROACH_USER. That ensures that regardless of the container being started interactively or not, the scripts in /docker-entrypoint-initdb.d get invoked.

[mattnappo]

Can I work on this issue?