SQLDesk 0.3.1

Fixes uploading a file, which 0.3.0 made worse rather than better. If you are on 0.3.0, move to this.

docker pull ghcr.io/bot-netizen/sqldesk:0.3.1

No migration, nothing to reconfigure — pull and restart.

What happened

0.3.0 fixed uploads by giving the server and the worker a shared volume at /app/uploads: the server saves the file, but the worker is what runs the query, and DuckDB opens the file by absolute path from there.

The same release also stopped shipping uploads/ inside the image, which was right in itself — a developer's own uploaded files had no business being in a published image.

Together they broke it. Docker takes a volume's ownership from the directory already present in the image. With that directory gone, Docker created the mount point owned by root, and the container does not run as root. Saving an upload then failed outright with a permission error — where before 0.3.0 the upload at least succeeded and only the query against it failed.

The image now creates /app/uploads owned by the user the container runs as, so the volume inherits that.

Why it was not caught

Neither the unit tests nor CI can see this. It is a property of the image and the volume together, and only appears when the documented install is run against the real published image. That is now the second bug of this shape, after the Postgres 18 data directory in 0.1.1.

Licence

SQLDesk is Apache 2.0. It is a fork of Redash, copyright © 2013–2020 Arik Fraimovich, licensed under BSD 2-Clause — that licence and its copyright notice are preserved verbatim in LICENSE.redash. See NOTICE for full attribution.

SQLDesk is an independent project. It is not affiliated with, endorsed by, or supported by the Redash project or its contributors.