InnoDB: Operating system error number 13 in a file operation.

gistfile1.txt

$ sudo docker run -it mysql:latest /bin/bash
Unable to find image 'mysql:latest' locally
latest: Pulling from mysql
25270607d748: Pull complete 
d118ad716ef1: Pull complete 
0985a1ea7675: Pull complete 
15959bd10e3d: Pull complete 
57c832a5f583: Pull complete 
92ba15de5dba: Pull complete 
0df34f74edfd: Pull complete 
284922e0435b: Pull complete 
c14920e9fcc2: Pull complete 
50806c71cd84: Pull complete 
d8bd0657b25f: Already exists 
a582cd499e0f: Already exists 
09338e0f5033: Already exists 
d10b70a30ff1: Already exists 
1758bec8365a: Already exists 
0c73937e713b: Already exists 
mysql:latest: The image you are pulling has been verified. Important: image verification is a tech preview feature and should not be relied on to provide security.
Digest: sha256:16de02081c408c41361126aaa718f91693688d39a216a74ac8dab841db050228
Status: Downloaded newer image for mysql:latest
root@292b950813f4:/# mysqld
2016-03-10T10:12:39.088740Z 0 [Note] mysqld (mysqld 5.7.11) starting as process 7 ...
2016-03-10T10:12:39.118272Z 0 [Note] InnoDB: PUNCH HOLE support available
2016-03-10T10:12:39.118312Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-03-10T10:12:39.118322Z 0 [Note] InnoDB: Uses event mutexes
2016-03-10T10:12:39.118330Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2016-03-10T10:12:39.118337Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.8
2016-03-10T10:12:39.118344Z 0 [Note] InnoDB: Using Linux native AIO
2016-03-10T10:12:39.122377Z 0 [Note] InnoDB: Number of pools: 1
2016-03-10T10:12:39.126649Z 0 [Note] InnoDB: Using CPU crc32 instructions
2016-03-10T10:12:39.141768Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2016-03-10T10:12:39.158260Z 0 [Note] InnoDB: Completed initialization of buffer pool
2016-03-10T10:12:39.160726Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2016-03-10T10:12:39.170794Z 0 [Note] InnoDB: The first innodb_system data file 'ibdata1' did not exist. A new tablespace will be created!
2016-03-10T10:12:39.171169Z 0 [ERROR] InnoDB: Operating system error number 13 in a file operation.
2016-03-10T10:12:39.171202Z 0 [ERROR] InnoDB: The error means mysqld does not have the access rights to the directory.
2016-03-10T10:12:39.171215Z 0 [ERROR] InnoDB: Operating system error number 13 in a file operation.
2016-03-10T10:12:39.171224Z 0 [ERROR] InnoDB: The error means mysqld does not have the access rights to the directory.
2016-03-10T10:12:39.171237Z 0 [ERROR] InnoDB: Cannot open datafile './ibdata1'
2016-03-10T10:12:39.171255Z 0 [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!
2016-03-10T10:12:39.171277Z 0 [ERROR] InnoDB: InnoDB Database creation was aborted with error Cannot open a file. You may need to delete the ibdata1 file before trying to start up again.
2016-03-10T10:12:39.771859Z 0 [ERROR] Plugin 'InnoDB' init function returned error.
2016-03-10T10:12:39.771920Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2016-03-10T10:12:39.771936Z 0 [ERROR] Failed to initialize plugins.
2016-03-10T10:12:39.771951Z 0 [ERROR] Aborting

2016-03-10T10:12:39.771998Z 0 [Note] Binlog end
2016-03-10T10:12:39.772120Z 0 [Note] Shutting down plugin 'MyISAM'
2016-03-10T10:12:39.772145Z 0 [Note] Shutting down plugin 'CSV'
2016-03-10T10:12:39.772152Z 0 [Note] Shutting down plugin 'keyring_file'
2016-03-10T10:12:39.775278Z 0 [Note] mysqld: Shutdown complete

How did you solve this?

@theAkito this is 4 years old, I have no idea 😁