fix: restore ../../sql mount path in single-node docker-compose so Postgres init scripts run

[mengw15]

What changes were proposed in this PR?

Restore the Postgres init-script volume mount in bin/single-node/docker-compose.yml from ./sql back to ../../sql

Any related issues, documentation, discussions?

close #4390

How was this PR tested?

manually

Was this PR authored or co-authored using generative AI tooling?

no

[bobbai00]

Can you try to create a symlink under bin/single-node pointing to sql/ at the root ? Basically mimic what bin/k8s/files did?

[mengw15]

Can you try to create a symlink under bin/single-node pointing to sql/ at the root ? Basically mimic what bin/k8s/files did?

Currently, in .github/workflows/create-release-candidate.yml
line 160-162

# Patch the SQL mount path for the self-contained bundle layout
# In the repo it's ../../sql (relative to bin/single-node/), in the bundle it's ./sql
sed -i 's|../../sql|./sql|g' "$BUNDLE_DIR/docker-compose.yml"

we sed ../../sql with ./sql

if we mimic the bin/k8s/files, we may need to adjust here as well

[bobbai00]

Can you try to create a symlink under bin/single-node pointing to sql/ at the root ? Basically mimic what bin/k8s/files did?

Currently, in .github/workflows/create-release-candidate.yml line 160-162

# Patch the SQL mount path for the self-contained bundle layout # In the repo it's ../../sql (relative to bin/single-node/), in the bundle it's ./sql sed -i 's|../../sql|./sql|g' "$BUNDLE_DIR/docker-compose.yml"

we sed ../../sql with ./sql

if we mimic the bin/k8s/files, we may need to adjust here as well

sure, you may adjust the CI as well. I feel '../../sql' should be avoided. Please try the symlink way and see if it works.

[mengw15]

sure, you may adjust the CI as well. I feel '../../sql' should be avoided. Please try the symlink way and see if it works.

I tested this by running docker compose up under bin/single-node, but this symlink way seems doesn't work. The reason could be Docker bind mounts preserve symlinks as-is rather than resolving them. Inside the container, the symlink target ../../../sql/xxx.sql resolves against the container's filesystem.

I remember we were using '../../sql' in the past

[bobbai00]

sure, you may adjust the CI as well. I feel '../../sql' should be avoided. Please try the symlink way and see if it works.

I tested this by running docker compose up under bin/single-node, but this symlink way seems doesn't work. The reason could be Docker bind mounts preserve symlinks as-is rather than resolving them. Inside the container, the symlink target ../../../sql/xxx.sql resolves against the container's filesystem.

I remember we were using '../../sql' in the past

Try: docker compose -f bin/single-node --project-directory . --env-file bin/single-node/.env up