Docker fresh install: web installer partially applies schema → multiple "Unknown column" / "Table doesn't exist" errors on login/dashboard

[Redroox]

[x]: This is a bug and not a question.

[x]: I understand that the best way to resolve this issue is to solve it and propose a Pull Request.

Describe the bug**

Fresh Docker install (using official image librebooking/librebooking:develop or :4.0.0) completes the web installer, writes config.php, creates admin account, but many schema upgrades fail partially or silently.
This results in numerous runtime errors when using the application (login succeeds, but almost every page/feature throws "Unknown column" or "Table doesn't exist" exceptions).

To Reproduce

1. Use a clean Docker Compose setup with librebooking/librebooking:develop (or :4.0.0) + mariadb:10.6
2. Run docker compose up -d
3. Open http://localhost:8081/Web/install/
4. Complete the installer (use correct DB credentials, create admin account, include sample data or not — both tested)
5. Finish installation → redirected to login
6. Log in as admin
7. Observe errors on dashboard, view resources, etc.

Observed errors (examples from logs after login/dashboard load):

• Unknown column 'display_page' in 'WHERE' → AnnouncementRepository.php:11
• Unknown column 'urp.permission_type' in 'SELECT' → UserRepository.php:662
• Unknown column 'grp.permission_type' in 'SELECT' → ResourceRepository.php:474
• Table 'librebooking.resource_images' doesn't exist → ResourceRepository.php:58
• Undefined array key "isdefault" → GroupRepository.php:298
• Earlier installer failures: column count mismatch in layouts insert, errno 194 tablespace missing during ALTERs, foreign key constraint blocks on DROP/DISCARD

Expected behavior
Fresh install should apply full schema (all tables + all upgrade scripts) without errors. Login and dashboard should load cleanly.

Actual behavior
Installer reports success on most steps, but many upgrade scripts fail (e.g. 2.7 schema.sql, 2.9 schema.sql, create-data.sql).
Result: partial schema → runtime SQL errors on nearly every page until missing columns/tables are manually added.

Environment

• Docker Compose on Windows 11 (Docker Desktop with WSL2 backend)
• App image: librebooking/librebooking:develop (also tested :4.0.0)
• DB image: mariadb:10.6 (also tested linuxserver/mariadb:10.6.13)
• PHP: 8.4.1 (from container logs)
• MariaDB: 10.6.13
• Browser: Firefox 147.0 (also tested Chrome)

Workaround / Fix that worked for me
Manually add missing columns/tables after installer completes:

• announcements.display_page → TINYINT(1) DEFAULT 1
• user_resource_permissions.permission_type → ENUM('view','reserve','manage') DEFAULT 'reserve'
• group_resource_permissions.permission_type → same as above
• resource_images table (full CREATE with matching resource_id SMALLINT(5) UNSIGNED)
• groups.isdefault → TINYINT(1) UNSIGNED DEFAULT 0

After patching ~5–6 pieces, the app works without errors.

Additional context

• Errors often related to InnoDB tablespace rename failures (errno 194) during ALTER in upgrade scripts → possibly Windows/Docker volume filesystem issue (9p)
• Sample data import fails on layouts insert (column count mismatch)
• Using :4.0.0 stable tag reduces (but does not eliminate) issues
• Related open issue: Database schema is missing tables and columns for tables #855 ("Database schema is missing tables and columns")

Would be great if the installer could be more resilient (e.g. continue on SQL failure, log detailed errors, or have a "repair schema" button).

Thanks for the great project — once patched it runs nicely!

[colisee]

Could you please create the issue on the github.com/librebooking/docker repository? Thank you Envoyé à partir de Outlook pour iOS<https://aka.ms/o0ukef>

…

________________________________ De : Redroox ***@***.***> Envoyé : Monday, January 26, 2026 4:03:29 PM À : LibreBooking/app ***@***.***> Cc : Subscribed ***@***.***> Objet : [LibreBooking/app] Docker fresh install: web installer partially applies schema → multiple "Unknown column" / "Table doesn't exist" errors on login/dashboard (Issue #925) [https://avatars.githubusercontent.com/u/1068012?s=20&v=4]Redroox created an issue (LibreBooking/librebooking#925)<#925> [x]: This is a bug and not a question. [x]: I understand that the best way to resolve this issue is to solve it and propose a Pull Request. Describe the bug** Fresh Docker install (using official image librebooking/librebooking:develop or :4.0.0) completes the web installer, writes config.php, creates admin account, but many schema upgrades fail partially or silently. This results in numerous runtime errors when using the application (login succeeds, but almost every page/feature throws "Unknown column" or "Table doesn't exist" exceptions). To Reproduce 1. Use a clean Docker Compose setup with librebooking/librebooking:develop (or :4.0.0) + mariadb:10.6 2. Run docker compose up -d 3. Open http://localhost:8081/Web/install/ 4. Complete the installer (use correct DB credentials, create admin account, include sample data or not — both tested) 5. Finish installation → redirected to login 6. Log in as admin 7. Observe errors on dashboard, view resources, etc. Observed errors (examples from logs after login/dashboard load): * Unknown column 'display_page' in 'WHERE' → AnnouncementRepository.php:11 * Unknown column 'urp.permission_type' in 'SELECT' → UserRepository.php:662 * Unknown column 'grp.permission_type' in 'SELECT' → ResourceRepository.php:474 * Table 'librebooking.resource_images' doesn't exist → ResourceRepository.php:58 * Undefined array key "isdefault" → GroupRepository.php:298 * Earlier installer failures: column count mismatch in layouts insert, errno 194 tablespace missing during ALTERs, foreign key constraint blocks on DROP/DISCARD Expected behavior Fresh install should apply full schema (all tables + all upgrade scripts) without errors. Login and dashboard should load cleanly. Actual behavior Installer reports success on most steps, but many upgrade scripts fail (e.g. 2.7 schema.sql, 2.9 schema.sql, create-data.sql). Result: partial schema → runtime SQL errors on nearly every page until missing columns/tables are manually added. Environment * Docker Compose on Windows 11 (Docker Desktop with WSL2 backend) * App image: librebooking/librebooking:develop (also tested :4.0.0) * DB image: mariadb:10.6 (also tested linuxserver/mariadb:10.6.13) * PHP: 8.4.1 (from container logs) * MariaDB: 10.6.13 * Browser: Firefox 147.0 (also tested Chrome) Workaround / Fix that worked for me Manually add missing columns/tables after installer completes: * announcements.display_page → TINYINT(1) DEFAULT 1 * user_resource_permissions.permission_type → ENUM('view','reserve','manage') DEFAULT 'reserve' * group_resource_permissions.permission_type → same as above * resource_images table (full CREATE with matching resource_id SMALLINT(5) UNSIGNED) * groups.isdefault → TINYINT(1) UNSIGNED DEFAULT 0 After patching ~5–6 pieces, the app works without errors. Additional context * Errors often related to InnoDB tablespace rename failures (errno 194) during ALTER in upgrade scripts → possibly Windows/Docker volume filesystem issue (9p) * Sample data import fails on layouts insert (column count mismatch) * Using :4.0.0 stable tag reduces (but does not eliminate) issues * Related open issue: #855<#855> ("Database schema is missing tables and columns") Would be great if the installer could be more resilient (e.g. continue on SQL failure, log detailed errors, or have a "repair schema" button). Thanks for the great project — once patched it runs nicely! — Reply to this email directly, view it on GitHub<#925>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/APKUZBPVRZNRR5AM42EWSVD4IYUEDAVCNFSM6AAAAACS5LE6E2VHI2DSMVQWIX3LMV43ASLTON2WKOZTHA2TMMZUGQ2DKNI>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[colisee]

Could you also share the docker-compose.yml file (if any) or the commands you ran to start the dockerized app? Envoyé à partir de Outlook pour iOS<https://aka.ms/o0ukef>

…

________________________________ De : Robin ALEXANDER ***@***.***> Envoyé : Monday, January 26, 2026 10:35:28 PM À : LibreBooking/app ***@***.***> Cc : Robin ALEXANDER ***@***.***>; Your activity ***@***.***> Objet : Re: [LibreBooking/app] Docker fresh install: web installer partially applies schema → multiple "Unknown column" / "Table doesn't exist" errors on login/dashboard (Issue #925) [https://avatars.githubusercontent.com/u/64310405?s=20&v=4]colisee left a comment (LibreBooking/librebooking#925)<#925 (comment)> Could you please create the issue on the github.com/librebooking/docker repository? Thank you Envoyé à partir de Outlook pour iOS<https://aka.ms/o0ukef>

________________________________ De : Redroox ***@***.***> Envoyé : Monday, January 26, 2026 4:03:29 PM À : LibreBooking/app ***@***.***> Cc : Subscribed ***@***.***> Objet : [LibreBooking/app] Docker fresh install: web installer partially applies schema → multiple "Unknown column" / "Table doesn't exist" errors on login/dashboard (Issue #925) [https://avatars.githubusercontent.com/u/1068012?s=20&v=4]Redroox created an issue (LibreBooking/librebooking#925)<#925> [x]: This is a bug and not a question. [x]: I understand that the best way to resolve this issue is to solve it and propose a Pull Request. Describe the bug** Fresh Docker install (using official image librebooking/librebooking:develop or :4.0.0) completes the web installer, writes config.php, creates admin account, but many schema upgrades fail partially or silently. This results in numerous runtime errors when using the application (login succeeds, but almost every page/feature throws "Unknown column" or "Table doesn't exist" exceptions). To Reproduce 1. Use a clean Docker Compose setup with librebooking/librebooking:develop (or :4.0.0) + mariadb:10.6 2. Run docker compose up -d 3. Open http://localhost:8081/Web/install/ 4. Complete the installer (use correct DB credentials, create admin account, include sample data or not — both tested) 5. Finish installation → redirected to login 6. Log in as admin 7. Observe errors on dashboard, view resources, etc. Observed errors (examples from logs after login/dashboard load): * Unknown column 'display_page' in 'WHERE' → AnnouncementRepository.php:11 * Unknown column 'urp.permission_type' in 'SELECT' → UserRepository.php:662 * Unknown column 'grp.permission_type' in 'SELECT' → ResourceRepository.php:474 * Table 'librebooking.resource_images' doesn't exist → ResourceRepository.php:58 * Undefined array key "isdefault" → GroupRepository.php:298 * Earlier installer failures: column count mismatch in layouts insert, errno 194 tablespace missing during ALTERs, foreign key constraint blocks on DROP/DISCARD Expected behavior Fresh install should apply full schema (all tables + all upgrade scripts) without errors. Login and dashboard should load cleanly. Actual behavior Installer reports success on most steps, but many upgrade scripts fail (e.g. 2.7 schema.sql, 2.9 schema.sql, create-data.sql). Result: partial schema → runtime SQL errors on nearly every page until missing columns/tables are manually added. Environment * Docker Compose on Windows 11 (Docker Desktop with WSL2 backend) * App image: librebooking/librebooking:develop (also tested :4.0.0) * DB image: mariadb:10.6 (also tested linuxserver/mariadb:10.6.13) * PHP: 8.4.1 (from container logs) * MariaDB: 10.6.13 * Browser: Firefox 147.0 (also tested Chrome) Workaround / Fix that worked for me Manually add missing columns/tables after installer completes: * announcements.display_page → TINYINT(1) DEFAULT 1 * user_resource_permissions.permission_type → ENUM('view','reserve','manage') DEFAULT 'reserve' * group_resource_permissions.permission_type → same as above * resource_images table (full CREATE with matching resource_id SMALLINT(5) UNSIGNED) * groups.isdefault → TINYINT(1) UNSIGNED DEFAULT 0 After patching ~5–6 pieces, the app works without errors. Additional context * Errors often related to InnoDB tablespace rename failures (errno 194) during ALTER in upgrade scripts → possibly Windows/Docker volume filesystem issue (9p) * Sample data import fails on layouts insert (column count mismatch) * Using :4.0.0 stable tag reduces (but does not eliminate) issues * Related open issue: #855<#855> ("Database schema is missing tables and columns") Would be great if the installer could be more resilient (e.g. continue on SQL failure, log detailed errors, or have a "repair schema" button). Thanks for the great project — once patched it runs nicely! — Reply to this email directly, view it on GitHub<#925>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/APKUZBPVRZNRR5AM42EWSVD4IYUEDAVCNFSM6AAAAACS5LE6E2VHI2DSMVQWIX3LMV43ASLTON2WKOZTHA2TMMZUGQ2DKNI>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***> — Reply to this email directly, view it on GitHub<#925 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/APKUZBORKOV2MCPPGRNQ4GL4I2CCBAVCNFSM6AAAAACS5LE6E2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTQMBRHA3DONBQGM>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>