Windmill #2353

Activity

1. MickLesk

   added

   task

   Ready For Testing

   and removed

   task

   on Oct 3, 2026
2. github-actions commented on Oct 3, 2026

   

   github-actionsBot

   on Oct 3, 2026 – with GitHub Actions

   Contributor

   More actions

   The Windmill script is ready for testing. Run it in the Proxmox VE shell (or on an Incus host) to create a container:

   bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVED/main/ct/windmill.sh)"
   

   Default credentials:
   Username: admin@windmill.dev
   Password: changeme

   Log in with admin@windmill.dev / changeme right after the install. Windmill then asks for a new superadmin account, which replaces the default one. Until you do that, anyone who reaches port 8000 can log in with the default credentials.
   Webhook URLs, OAuth redirects and links in emails are built from BASE_URL in /opt/windmill_data/.env, which points at the container IP. Change it when the IP changes or Windmill sits behind a reverse proxy or domain, then run systemctl restart windmill. A Base URL set in the instance settings takes precedence.
   Python (through uv, which downloads the Python version on first use), TypeScript on Bun, Bash, DuckDB and SQL scripts run out of the box. The other languages the editor offers (TypeScript on Deno, Go, PHP, PowerShell, Rust, C#, Java, Ansible and more) need their runtime installed in the container first.
   Server and worker share one process with a single worker, so jobs run one at a time. For parallel jobs, run more Windmill processes with MODE=worker against the same database.
   The windmill database role has no CREATEDB or CREATEROLE privilege, so the Custom instance database option for Data Tables and DuckLake fails with permission denied. Point Data Tables at a PostgreSQL resource instead.

   Note: This is not in the official repo yet—it's just a dev version! After merging into ProxmoxVE, it will need to be recreated.

   Discord testing thread: https://discord.com/channels/1302816934508630047/1556046092452495512
3. eliah-w commented on Oct 27, 2026

   

   eliah-w

   on Oct 27, 2026

   More actions

   The update script fails because release v1.850.0 has windmill_duckdb_runner, but no old .so asset. Upstream replaced the library but the updater still requests it.

   Upstream change

   the Docker, RHEL 8/9 and Windows builds ship the runner next to windmill instead of libwindmill_duckdb_ffi_internal.so / .dll, and the release workflows attach it.

   windmill pull request #11780

   Updater Log

   ✔️ Update available: windmill 1.846.1 -> 1.850.0 (the last run did not finish, doing it again)
   ✔️ Stopped Windmill
   ⏳ Update Node.js 24Hit:1 http://deb.debian.org/debian trixie InRelease
   Hit:2 http://deb.debian.org/debian trixie-updates InRelease
   Hit:3 http://security.debian.org/ trixie-security InRelease
   Hit:4 https://deb.nodesource.com/node_24.x nodistro InRelease
   Hit:5 https://apt.postgresql.org/pub/repos/apt trixie-pgdg InRelease
   Reading package lists...
   Building dependency tree...
   Reading state information...
   All packages are up to date.
   Reading package lists...
   Building dependency tree...
   Reading state information...
   nodejs is already the newest version (24.22.1-1nodesource1).
   0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
   
   changed 10 packages in 1s
   ✔️ Update Node.js 24 (npm 12.2.1)
   ⏳ Updating bun to latest version
   changed 2 packages in 2s
   ✔️ Updated bun
   ✔️ Deployed: windmill (1.850.0)
   ✖️ No asset matching 'libwindmill_duckdb_ffi_internal.so' found
   ✖️ in line 2354: exit code 252 (App: Required file or resource not found): while executing command fetch_and_deploy_release github "$1" "$2" "3: −tarball" "3: −tarball" "{4:-latest}" "5:−""5:−""{6:-}" "${7:-}"
   ```
   
4. MickLesk commented on Oct 28, 2026

   

   MickLesk

   on Oct 28, 2026

   MemberAuthor

   More actions

   Fixed in a0922fa: install and update now fetch windmill_duckdb_runner next to the windmill binary instead of the old .so

   👍React with 👍1Reacted by Eliah