Docker Community Forums

Share and learn in the Docker community.

Official mysql image won't run


(Voldemortensen) #1

I’m trying to run a container using the official mysql container. Every time I try the mysql_install_db fails because the container OOMs. All of my other containers were working fine and this problem suddenly started. Now I can’t create any containers? Any ideas?

Running mysql_install_db …
Installing MySQL system tables…2015-04-22 19:57:19 0 [Note] /usr/sbin/mysqld (mysqld 5.6.24) starting as process 15 …
2015-04-22 19:57:19 15 [Warning] Buffered warning: Changed limits: max_open_files: 1024 (requested 5000)

2015-04-22 19:57:19 15 [Warning] Buffered warning: Changed limits: table_open_cache: 431 (requested 2000)

2015-04-22 19:57:19 15 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-04-22 19:57:19 15 [Note] InnoDB: The InnoDB memory heap is disabled
2015-04-22 19:57:19 15 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2015-04-22 19:57:19 15 [Note] InnoDB: Memory barrier is not used
2015-04-22 19:57:19 15 [Note] InnoDB: Compressed tables use zlib 1.2.7
2015-04-22 19:57:19 15 [Note] InnoDB: Using Linux native AIO
2015-04-22 19:57:19 15 [Note] InnoDB: Using CPU crc32 instructions
2015-04-22 19:57:19 15 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2015-04-22 19:57:19 15 [Note] InnoDB: Completed initialization of buffer pool
2015-04-22 19:57:19 15 [Note] InnoDB: The first specified data file ./ibdata1 did not exist: a new database to be created!
2015-04-22 19:57:19 15 [Note] InnoDB: Setting file ./ibdata1 size to 12 MB
2015-04-22 19:57:19 15 [Note] InnoDB: Database physically writes the file full: wait…
2015-04-22 19:57:19 7fb63ab4b7202015-04-22 19:57:19 15 [ERROR] InnoDB: Failure of system call pwrite(). Operating system error number is 28.
InnoDB: Error number 28 means ‘No space left on device’.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
2015-04-22 19:57:19 15 [ERROR] InnoDB: Error in creating ./ibdata1: probably out of disk space
2015-04-22 19:57:19 15 [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!
2015-04-22 19:57:19 15 [ERROR] Plugin ‘InnoDB’ init function returned error.
2015-04-22 19:57:19 15 [ERROR] Plugin ‘InnoDB’ registration as a STORAGE ENGINE failed.
2015-04-22 19:57:19 15 [ERROR] Unknown/unsupported storage engine: InnoDB
2015-04-22 19:57:19 15 [ERROR] Aborting

2015-04-22 19:57:19 15 [Note] Binlog end
2015-04-22 19:57:19 15 [Note] /usr/sbin/mysqld: Shutdown complete


(Kuchaev Ilya) #2

Isn’t that an exact issue? Do you have enough disk space on the host?


(Voldemortensen) #3

According to docker info I have plenty of space.
Data Space Used: 1.481 GB
Data Space Total: 107.4 GB
Metadata Space Used: 3.469 MB
Metadata Space Total: 2.147 GB


(Voldemortensen) #4

As a follow up, I found /var/lib/docker had completely filled my host. It seems that docker isn’t deleting the filesystems after containers are destroyed.


(Andy Rothfusz) #5

Please look for a github issue that matches your symptoms. https://github.com/docker/docker/issues/12265 looked close to me.