Scripts from docker-entrypoint-initdb.d are not executed when using --store=type=mem,size=0.25 for start-single-node

[janpio]

We have successfully been using an adapted Docker image with a file in /docker-entrypoint-initdb.d to create a user and apply the suggested testing configuration: https://github.com/prisma/engine-images/blob/7695bfcc990b5f91cf5d86b15ec95fc3b129f709/cockroach/cockroach.Dockerfile

Now we were also recommended to use --store=type=mem,size=0.25 as an additional argument to start-single-node --insecure and noticed that a) the user is not present any more and b) all the configuration is default - so I think our .sql file from our image is not run correctly.

Reproduction is possible via this docker-compose:

version: "3"
services:
  test-db-cockroachdb:
    image: prismagraphql/build:cockroach-custom
    restart: always
    command: start-single-node --insecure
    ports:
      - "26257:26257"
    networks:
      - engine-tests

  test-db-cockroachdb-mem:
    image: prismagraphql/build:cockroach-custom
    restart: always
    command: start-single-node --insecure --store=type=mem,size=0.25
    ports:
      - "26258:26257"
    networks:
      - engine-tests

networks:
  engine-tests: null

The prismagraphql/build:cockroach-custom is our customized image that adds the .sql file to cockroachdb/cockroach-unstable:v22.1.0-alpha.1, it is built via https://github.com/prisma/engine-images/blob/7695bfcc990b5f91cf5d86b15ec95fc3b129f709/cockroach/cockroach.Dockerfile linked above.

Jira issue: CRDB-15693

[blathers-crl]

Hello, I am Blathers. I am here to help you get the issue triaged.

It looks like you have not filled out the issue in the format of any of our templates. To best assist you, we advise you to use one of these templates.

I have CC'd a few people who may be able to assist you:

• @cockroachdb/sql-experience (found keywords: prisma)

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 otan.}

[ZhouXing19]

Thanks for making this issue! We definitely missed the case where memory is used for storage.

The key issue is that currently the datasets created in the init process are stored on disk, and they are inaccessible if the "real" server is started with storage in memory.

For the container initialization, the current logic is:

1. start_init_server: start the single-node server in the background, with default on-disk storage setting;
2. run_init_queries: create default db and user, and run the init scripts saved in docker-entrypoint-initdb.d;
3. stop the init server and restart the server with given parameters (e.g. --store-type=mem... in this case) in foreground.

The possible workaround is to start and keep running the init server with the given parameters, and eliminate the "stop and restart" step. However, this can be a bit tricky, because without a foreground process, the container would automatically exit after executing all logic in DockerFile.

I'm still investigating more solutions. Will reply under this thread once I find a solid one.

[janpio]

Ah, I see - thanks for the acknowledgement and explanation.

Prisma will keep using the non memory option then for now.