Thanks for the report. First, a general note: JIRA is our issue tracker for confirmed bugs and feature requests, not a support channel. Questions, troubleshooting and "is this a bug?" discussions should be raised on the forum at \[[https://forum.xwiki.org|https://forum.xwiki.org]\] instead, where the community can help. Please use the forum for this kind of investigation.
On the substance, this doesn't appear to be a bug in the XWiki Docker image or in XWiki's MySQL/MariaDB support:
* You mention that the XWiki instance itself works fine \(creating pages, installing extensions\). That confirms the JDBC connection and the database privileges for the main wiki are correct \-\- so this isn't a case of XWiki mishandling MySQL/MariaDB privileges. * "Empty databases in phpMyAdmin even as root" almost certainly means phpMyAdmin is connected to a _different_ database server \(or schema view\) than the one used by the container. XWiki stores its data in the {{xwiki}} schema plus one additional schema per subwiki; if the application works, the tables do exist. * {{Error 13: Permission Denied}} is a _filesystem_ error \(errno 13 = {{EACCES}}\), not a database\-privilege error. Creating a subwiki also writes a Solr core under the permanent directory \({{/usr/local/xwiki}}\). When the image is deployed via a GitLab CI/CD runner, the bind\-mounted volume can get host ownership that the Tomcat process inside the container cannot write to \-\- which matches the file\-ownership behaviour you observed. This is a deployment/volume\-mount concern in your environment rather than something the image controls. * For the database side of subwiki creation, the {{docker\-compose}} setup already ships an {{init.sql}} that runs {{grant all privileges on _._ to xwiki@'%'}} \(added in XDOCKER\-118\), and this is documented in the README. That grants the privileges required to create the new schemas that subwikis need.
We test MySQL and MariaDB automatically and manually and they work fine. Since the report is based on a self\-contradicting "core bug" claim and no logs/stack trace were provided, I'm closing this as Incomplete. If, after investigating on the forum, a genuine reproducible bug is identified, please open a fresh issue with the full {{Error 13}} stack trace, the XWiki logs, and details of how you mount and set ownership on the volumes under your GitLab runner.
Vincent Massol on 18/Jul/26 17:18
Thanks for the report. First, a general note: JIRA is our issue tracker for confirmed bugs and feature requests, not a support channel. Questions, troubleshooting and "is this a bug?" discussions should be raised on the forum at \ [[https://forum.xwiki.org|https://forum.xwiki.org]\] instead, where the community can help. Please use the forum for this kind of investigation.
On the substance, this doesn't appear to be a bug in the XWiki Docker image or in XWiki's MySQL/MariaDB support:
* You mention that the XWiki instance itself works fine \ (creating pages, installing extensions\). That confirms the JDBC connection and the database privileges for the main wiki are correct \ -\- so this isn't a case of XWiki mishandling MySQL/MariaDB privileges. * "Empty databases in phpMyAdmin even as root" almost certainly means phpMyAdmin is connected to a _different_ database server \ (or schema view\) than the one used by the container. XWiki stores its data in the {{xwiki}} schema plus one additional schema per subwiki; if the application works, the tables do exist. * {{Error 13: Permission Denied}} is a _filesystem_ error \ (errno 13 = {{EACCES}}\), not a database\-privilege error. Creating a subwiki also writes a Solr core under the permanent directory \ ({{/usr/local/xwiki}}\). When the image is deployed via a GitLab CI/CD runner, the bind\-mounted volume can get host ownership that the Tomcat process inside the container cannot write to \ -\- which matches the file\-ownership behaviour you observed. This is a deployment/volume\-mount concern in your environment rather than something the image controls. * For the database side of subwiki creation, the {{docker\-compose}} setup already ships an {{init.sql}} that runs {{grant all privileges on _._ to xwiki@'%'}} \ (added in XDOCKER\-118\), and this is documented in the README. That grants the privileges required to create the new schemas that subwikis need.
We test MySQL and MariaDB automatically and manually and they work fine. Since the report is based on a self\-contradicting "core bug" claim and no logs/stack trace were provided, I'm closing this as Incomplete. If, after investigating on the forum, a genuine reproducible bug is identified, please open a fresh issue with the full {{Error 13}} stack trace, the XWiki logs, and details of how you mount and set ownership on the volumes under your GitLab runner.
Vincent Massol on 18/Jul/26 17:20
Thanks for the report. First, a general note: JIRA is our issue tracker for confirmed bugs and feature requests, not a support channel. Questions, troubleshooting and "is this a bug?" discussions should be raised on the forum at \[[https://forum.xwiki.org|https://forum.xwiki.org]\] instead, where the community can help. Please use the forum for this kind of investigation.
On the substance, this doesn't appear to be a bug in the XWiki Docker image or in XWiki's MySQL/MariaDB support:
* You mention that the XWiki instance itself works fine \ (creating pages, installing extensions\). That confirms the JDBC connection and the database privileges for the main wiki are correct \ -\- so this isn't a case of XWiki mishandling MySQL/MariaDB privileges. * "Empty databases in phpMyAdmin even as root" almost certainly means phpMyAdmin is connected to a _different_ database server \ (or schema view\) than the one used by the container. XWiki stores its data in the {{xwiki}} schema plus one additional schema per subwiki; if the application works, the tables do exist. * {{Error 13: Permission Denied}} is a _filesystem_ error \ (errno 13 = {{EACCES}}\), not a database\-privilege error. Creating a subwiki also writes a Solr core under the permanent directory \ ({{/usr/local/xwiki}}\). When the image is deployed via a GitLab CI/CD runner, the bind\-mounted volume can get host ownership that the Tomcat process inside the container cannot write to \ -\- which matches the file\-ownership behaviour you observed. This is a deployment/volume\-mount concern in your environment rather than something the image controls. * For the database side of subwiki creation, the {{docker\-compose}} setup already ships an {{init.sql}} that runs {{grant all privileges on _._ to xwiki@'%'}} \ (added in XDOCKER\-118\), and this is documented in the README. That grants the privileges required to create the new schemas that subwikis need.
We test MySQL and MariaDB automatically and manually and they work fine. Since the report is based on a self\-contradicting "core bug" claim and no logs/stack trace were provided, I'm closing this as Incomplete. If, after investigating on the forum, a genuine reproducible bug is identified, please open a fresh issue with the full {{Error 13}} stack trace, the XWiki logs, and details of how you mount and set ownership on the volumes under your GitLab runner.
Vincent Massol on 18/Jul/26 17:20
Thanks for the report. First, a general note: JIRA is our issue tracker for confirmed bugs and feature requests, not a support channel. Questions, troubleshooting and "is this a bug?" discussions should be raised on the forum at \[[https://forum.xwiki.org|https://forum.xwiki.org]\] instead, where the community can help. Please use the forum for this kind of investigation.
On the substance, this doesn't appear to be a bug in the XWiki Docker image or in XWiki's MySQL/MariaDB support:
* You mention that the XWiki instance itself works fine \(creating pages, installing extensions\). That confirms the JDBC connection and the database privileges for the main wiki are correct \-\- so this isn't a case of XWiki mishandling MySQL/MariaDB privileges. * "Empty databases in phpMyAdmin even as root" almost certainly means phpMyAdmin is connected to a _different_ database server \(or schema view\) than the one used by the container. XWiki stores its data in the {{xwiki}} schema plus one additional schema per subwiki; if the application works, the tables do exist. * {{Error 13: Permission Denied}} is a _filesystem_ error \(errno 13 = {{EACCES}}\), not a database\-privilege error. Creating a subwiki also writes a Solr core under the permanent directory \({{/usr/local/xwiki}}\). When the image is deployed via a GitLab CI/CD runner, the bind\-mounted volume can get host ownership that the Tomcat process inside the container cannot write to \-\- which matches the file\-ownership behaviour you observed. This is a deployment/volume\-mount concern in your environment rather than something the image controls. * For the database side of subwiki creation, the {{docker\-compose}} setup already ships an {{init.sql}} that runs {{grant all privileges on _._ to xwiki@'%'}} \(added in XDOCKER\-118\), and this is documented in the README. That grants the privileges required to create the new schemas that subwikis need.
We test MySQL and MariaDB automatically and manually and they work fine. Since the report is based on a self\-contradicting "core bug" claim and no logs/stack trace were provided, I'm closing this as Incomplete. If, after investigating on the forum, a genuine reproducible bug is identified, please open a fresh issue with the full {{Error 13}} stack trace, the XWiki logs, and details of how you mount and set ownership on the volumes under your GitLab runner.
Vincent Massol on 18/Jul/26 17:21
Thanks for the report. First, a general note: JIRA is our issue tracker for confirmed bugs and feature requests, not a support channel. Questions, troubleshooting and "is this a bug?" discussions should be raised on the forum at \[[https://forum.xwiki.org|https://forum.xwiki.org]\] instead, where the community can help. Please use the forum for this kind of investigation.
On the substance, this doesn't appear to be a bug in the XWiki Docker image or in XWiki's MySQL/MariaDB support:
* You mention that the XWiki instance itself works fine \ (creating pages, installing extensions\). That confirms the JDBC connection and the database privileges for the main wiki are correct \ -\- so this isn't a case of XWiki mishandling MySQL/MariaDB privileges. * "Empty databases in phpMyAdmin even as root" almost certainly means phpMyAdmin is connected to a _different_ database server \ (or schema view\) than the one used by the container. XWiki stores its data in the {{xwiki}} schema plus one additional schema per subwiki; if the application works, the tables do exist. * {{Error 13: Permission Denied}} is a _filesystem_ error \ (errno 13 = {{EACCES}}\), not a database\-privilege error. Creating a subwiki also writes a Solr core under the permanent directory \ ({{/usr/local/xwiki}}\). When the image is deployed via a GitLab CI/CD runner, the bind\-mounted volume can get host ownership that the Tomcat process inside the container cannot write to \ -\- which matches the file\-ownership behaviour you observed. This is a deployment/volume\-mount concern in your environment rather than something the image controls. * For the database side of subwiki creation, the {{docker\-compose}} setup already ships an {{init.sql}} that runs {{grant all privileges on _._ to xwiki@'%'}} \ (added in XDOCKER\-118\), and this is documented in the README. That grants the privileges required to create the new schemas that subwikis need.
We test MySQL and MariaDB automatically and manually and they work fine. Since the report is based on a self\-contradicting "core bug" claim and no logs/stack trace were provided, I'm closing this as Incomplete. If, after investigating on the forum, a genuine reproducible bug is identified, please open a fresh issue with the full {{Error 13}} stack trace, the XWiki logs, and details of how you mount and set ownership on the volumes under your GitLab runner.
Vincent Massol on 18/Jul/26 17:21
Thanks for the report. First, a general note: JIRA is our issue tracker for confirmed bugs and feature requests, not a support channel. Questions, troubleshooting and "is this a bug?" discussions should be raised on the forum at \[[https://forum.xwiki.org|https://forum.xwiki.org]\] instead, where the community can help. Please use the forum for this kind of investigation.
On the substance, this doesn't appear to be a bug in the XWiki Docker image or in XWiki's MySQL/MariaDB support:
* You mention that the XWiki instance itself works fine \(creating pages, installing extensions\). That confirms the JDBC connection and the database privileges for the main wiki are correct \-\- so this isn't a case of XWiki mishandling MySQL/MariaDB privileges. * "Empty databases in phpMyAdmin even as root" almost certainly means phpMyAdmin is connected to a _different_ database server \(or schema view\) than the one used by the container. XWiki stores its data in the {{xwiki}} schema plus one additional schema per subwiki; if the application works, the tables do exist. * {{Error 13: Permission Denied}} is a _filesystem_ error \(errno 13 = {{EACCES}}\), not a database\-privilege error. Creating a subwiki also writes a Solr core under the permanent directory \({{/usr/local/xwiki}}\). When the image is deployed via a GitLab CI/CD runner, the bind\-mounted volume can get host ownership that the Tomcat process inside the container cannot write to \-\- which matches the file\-ownership behaviour you observed. This is a deployment/volume\-mount concern in your environment rather than something the image controls. * For the database side of subwiki creation, the {{docker\-compose}} setup already ships an {{init.sql}} that runs {{grant all privileges on _._ to xwiki@'%'}} \(added in XDOCKER\-118\), and this is documented in the README. That grants the privileges required to create the new schemas that subwikis need.
We test MySQL and MariaDB automatically and manually and they work fine. Since the report is based on a self\-contradicting "core bug" claim and no logs/stack trace were provided, I'm closing this as Incomplete. If, after investigating on the forum, a genuine reproducible bug is identified, please open a fresh issue with the full {{Error 13}} stack trace, the XWiki logs, and details of how you mount and set ownership on the volumes under your GitLab runner.
Vincent Massol on 18/Jul/26 17:23
Thanks for the report. First, a general note: JIRA is our issue tracker for confirmed bugs and feature requests, not a support channel. Questions, troubleshooting and "is this a bug?" discussions should be raised on the forum at \[[https://forum.xwiki.org|https://forum.xwiki.org]\] instead, where the community can help. Please use the forum for this kind of investigation.
On the substance, this doesn't appear to be a bug in the XWiki Docker image or in XWiki's MySQL/MariaDB support:
* You mention that the XWiki instance itself works fine \(creating pages, installing extensions\). That confirms the JDBC connection and the database privileges for the main wiki are correct \-\- so this isn't a case of XWiki mishandling MySQL/MariaDB privileges. * "Empty databases in phpMyAdmin even as root" almost certainly means phpMyAdmin is connected to a _different_ database server \(or schema view\) than the one used by the container. XWiki stores its data in the {{xwiki}} schema plus one additional schema per subwiki; if the application works, the tables do exist. * {{Error 13: Permission Denied}} is a _filesystem_ error \(errno 13 = {{EACCES}}\), not a database\-privilege error. Creating a subwiki also writes a Solr core under the permanent directory \({{/usr/local/xwiki}}\). When the image is deployed via a GitLab CI/CD runner, the bind\-mounted volume can get host ownership that the Tomcat process inside the container cannot write to \-\- which matches the file\-ownership behaviour you observed. This is a deployment/volume\-mount concern in your environment rather than something the image controls. * For the database side of subwiki creation, the {{docker\-compose}} setup already ships an {{init.sql}} that runs {{grant all privileges on _._ to xwiki@'%'}} \(added in XDOCKER\-118\), and this is documented in the README. That grants the privileges required to create the new schemas that subwikis need.
We test MySQL and MariaDB automatically and manually and they work fine. Since the report is based on a self\-contradicting "core bug" claim and no logs/stack trace were provided, I'm closing this as Incomplete. If, after investigating on the forum, a genuine reproducible bug is identified, please open a fresh issue with the full {{Error 13}} stack trace, the XWiki logs, and details of how you mount and set ownership on the volumes under your GitLab runner.
This message was sent by Atlassian Jira (v9.3.0#930000-sha1:287aeb6)
If image attachments aren't displayed, see this article.
