Problem with Kubernetes and Mounted Volume

[SheppardX]

Hey i got an this error, can some one help me ?

2017-05-03 15:50:07 140032113076160 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-05-03 15:50:07 140032113076160 [Note] InnoDB: The InnoDB memory heap is disabled
2017-05-03 15:50:07 140032113076160 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-05-03 15:50:07 140032113076160 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2017-05-03 15:50:07 140032113076160 [Note] InnoDB: Compressed tables use zlib 1.2.8
2017-05-03 15:50:07 140032113076160 [Note] InnoDB: Using Linux native AIO
2017-05-03 15:50:07 140032113076160 [Note] InnoDB: Using SSE crc32 instructions
2017-05-03 15:50:07 140032113076160 [Note] InnoDB: Initializing buffer pool, size = 256.0M
2017-05-03 15:50:08 140032113076160 [Note] InnoDB: Completed initialization of buffer pool
2017-05-03 15:50:08 140032113076160 [Warning] InnoDB: Failed to set O_DIRECT on file ./ibdata1: OPEN: Invalid argument, continuing anyway. O_DIRECT is known to result in 'Invalid argument' on Linux on tmpfs, see MySQL Bug#26662.
2017-05-03 15:50:08 140032113076160 [Note] InnoDB: Restoring page 0 of tablespace 0
2017-05-03 15:50:08 140032113076160 [Warning] InnoDB: Doublewrite does not have page_no=0 of space: 0
2017-05-03 15:50:08 140032113076160 [ERROR] InnoDB: space header page consists of zero bytes in data file ./ibdata1
2017-05-03 15:50:08 140032113076160 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!
2017-05-03 15:50:08 140032113076160 [ERROR] Plugin 'InnoDB' init function returned error.
2017-05-03 15:50:08 140032113076160 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-05-03 15:50:08 140032113076160 [Note] Plugin 'FEEDBACK' is disabled.
2017-05-03 15:50:08 140032113076160 [ERROR] Could not open mysql.plugin table. Some plugins may be not loaded
2017-05-03 15:50:08 140032113076160 [ERROR] Unknown/unsupported storage engine: InnoDB
2017-05-03 15:50:08 140032113076160 [ERROR] Aborting

[yosifkit]

I would guess permissions on the volume? You can run the image with a specific --user (related: #38 (comment)).

[tianon]

For further help debugging, I'd recommend trying the Docker Community Forums, the Docker Community Slack, or Stack Overflow.