Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Owncloud doesn't start #35

Closed
vashchenkov opened this issue Dec 20, 2017 · 16 comments

Comments

@vashchenkov
Copy link

commented Dec 20, 2017

I try to use this docker-compose.yml file. But owncloud can't be successfully configured. While updating old DB or creating new DB error 1036 has appear

General error: 1036 Table '/tmp/#sql_b6_0.MAI' is read only

After that I have set another image for db service
db: image: mariadb:10.3.2
And owncloud has been successfully started.

@tboerger

This comment has been minimized.

Copy link
Member

commented Feb 5, 2018

Please start with a clean environment one more time, I have replaced the host volumes with named docker volumes.

@tboerger tboerger closed this Feb 5, 2018

@admlko

This comment has been minimized.

Copy link

commented Mar 26, 2018

I can confirm this still exists with clean installation. I am following ownCloud documentation to set it up with Docker, and it doesn't go into login screen as stated here but it goes to first installation wizard instead (asking admin, data storage and db information).
If I fill them out, I get the same error as OP.

Here's the relevant information from the logs:

owncloud_1  | Installing server database...
owncloud_1  | Error while trying to create admin user: An exception occurred while executing 'SELECT COLUMN_NAME AS Field, COLUMN_TYPE AS Type, IS_NULLABLE AS `Null`, COLUMN_KEY AS `Key`, COLUMN_DEFAULT AS `Default`, EXTRA AS Extra, COLUMN_COMMENT AS Comment, CHARACTER_SET_NAME AS CharacterSet, COLLATION_NAME AS Collation FROM information_schema.COLUMNS WHERE TABLE_SCHEMA = 'owncloud' AND TABLE_NAME = 'oc_appconfig'':
owncloud_1  | 
owncloud_1  | SQLSTATE[HY000]: General error: 1036 Table '/tmp/#sql_12a_0.MAI' is read only
@tboerger

This comment has been minimized.

Copy link
Member

commented Mar 27, 2018

Than you should provide more information or just replace the webhippie/mariadb with mariadb.

@admlko

This comment has been minimized.

Copy link

commented Mar 27, 2018

You are correct that replacing webhippie/mariadb with official mariadb fixed the issue.
Though it would be nice to provide useful information to fix the issue.

The OS is a clean minimal installation of CentOS 7 with Docker installed from their repo and followed ownCloud official docker documentation. SELinux is of course enabled, and turning it off is not a solution :)

You have to excuse my inability to provide more useful information by myself as this is my first Docker experiment.

@andystoeggle

This comment has been minimized.

Copy link

commented Mar 27, 2018

I face the same issue. The error getting thrown is:
Error while trying to create admin user: An exception occurred while executing 'SELECT COLUMN_NAME AS Field, COLUMN_TYPE AS Type, IS_NULLABLE AS 'Null', COLUMN_KEY AS 'Key', COLUMN_DEFAULT AS 'Default', EXTRA AS Extra, COLUMN_COMMENT AS Comment, CHARACTER_SET_NAME AS CharacterSet, COLLATION_NAME AS Collation FROM information_schema.COLUMNS WHERE TABLE_SCHEMA = 'owncloud' AND TABLE_NAME = 'oc_appconfig'': SQLSTATE[HY000]: General error: 1036 Table '/tmp/#sql_12c_0.MAI' is read only
I have to use docker-compose v2 so I removed the healtcheck-Sections in each service, but I don't think this is responsible for the error. Additionally, my mariadb-Container runs on another host as the owncloud-Container but the connection seems to work properly

@tboerger

This comment has been minimized.

Copy link
Member

commented Mar 27, 2018

@admlko looks like mariadb got some fix for apparmor hosts which webhippie/mariadb seems to be lacking because this issue only happens on redhat derivatives that got apparmor enabled, looks like I have to mention that within the readme until I get the webhippie/mariadb fixed.

@andystoeggle I think you are hitting a different issue, the docker-compose config is configured to enable utf8mb4, but to get this working it also requires changes to the used database. Please try to disable the utf8mb4 env variable and retry it with a clean state.

@andystoeggle

This comment has been minimized.

Copy link

commented Mar 28, 2018

@tboerger Thank you very much for the hint. I tried a few things and found this SO conversation - I think this bug causes the problem. I'll work around with the official mariadb image (which is basically working) and setup the database manually.

@dschmidt

This comment has been minimized.

Copy link

commented Apr 1, 2018

@tboerger Isn't this issue valid then if the composer file does not work on all hosts? (I'm implying it should be reopened)

For anyone else who runs into this and for the time being wants to replace webhippie/mariadb with mariadb: The env vars for mariadb are called MYSQL_ and not MARIADB_ as for webhippie/mariadb.

@tboerger

This comment has been minimized.

Copy link
Member

commented Apr 1, 2018

@tboerger Isn't this issue valid then if the composer file does not work on all hosts? (I'm implying it should be reopened)

If the issue really relates to the docker-compose file, yes... But this is not really related to the docker-compose file itself, it's related to some kind of security limitation of the host system.

@dschmidt

This comment has been minimized.

Copy link

commented Apr 1, 2018

Ah, apparently this is a duplicate of #46 which already has more detailed information about how to get it work. So yeah, we can keep this closed ;-)

@tboerger

This comment has been minimized.

Copy link
Member

commented Apr 1, 2018

When I found a proper solution I will give an update.

@StefanWeiss2787

This comment has been minimized.

Copy link

commented Aug 24, 2018

How to replace that webhippie/mariadb with mariadb?

@oldthreefeng

This comment has been minimized.

Copy link

commented Sep 29, 2018

How to replace that webhippie/mariadb with mariadb?

Have you solved this problem?

@StefanWeiss2787

This comment has been minimized.

Copy link

commented Sep 30, 2018

How to replace that webhippie/mariadb with mariadb?

Have you solved this problem?

Yeah for me was fairly easy. Ditch the official owncloud docker install and just go straight for the image provided... no dokcer-compose no nothing just get the docker image (i think this: https://hub.docker.com/_/owncloud/) up and running

@tboerger

This comment has been minimized.

Copy link
Member

commented Sep 30, 2018

Yeah for me was fairly easy. Ditch the official owncloud docker install and just go straight for the image provided... no dokcer-compose no nothing just get the docker image (i think this: https://hub.docker.com/_/owncloud/) up and running

The "official" image is not maintained by ownCloud, it's maintained by Docker Inc, besides that this image is deprecated.

Have you solved this problem?

Just replace webhippie/mariadb with mariadb and replace the env variables.

@mario462

This comment has been minimized.

Copy link

commented Apr 9, 2019

@tboerger Isn't this issue valid then if the composer file does not work on all hosts? (I'm implying it should be reopened)

For anyone else who runs into this and for the time being wants to replace webhippie/mariadb with mariadb: The env vars for mariadb are called MYSQL_ and not MARIADB_ as for webhippie/mariadb.

Quick note here, don't take this literally 😅I just spent a good amount of time figuring out why I didn't have access to my database. Turns out mysql env variable for user is MYSQL_USER, which is named MARIADB_USERNAME for mariadb. Hope this helps someone 😁

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
8 participants
You can’t perform that action at this time.