Esta mañana intento instalar Docker en mi computadora portátil (windows10), (Mi Docker usa hyper-v)
Intento usar este docker-compose básico
version: '2' services: mariadb: image: mariadb container_name: mariadb ports: - "3306:3306" volumes: - ./mysql1/:/var/lib/mysql environment: MYSQL_USER : root MYSQL_ROOT_PASSWORD: rootTengo un error al ejecutar:
docker-compose up Creating mariadb Attaching to mariadb mariadb | 2017-04-04 8:29:00 140557637724096 [Note] mysqld (mysqld 10.1.22-MariaDB-1~jessie) starting as process 1 ... mariadb | 2017-04-04 8:29:00 140557637724096 [Note] InnoDB: Using mutexes to ref count buffer pool pages mariadb | 2017-04-04 8:29:00 140557637724096 [Note] InnoDB: The InnoDB memory heap is disabled mariadb | 2017-04-04 8:29:00 140557637724096 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins mariadb | 2017-04-04 8:29:00 140557637724096 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier mariadb | 2017-04-04 8:29:00 140557637724096 [Note] InnoDB: Compressed tables use zlib 1.2.8 mariadb | 2017-04-04 8:29:00 140557637724096 [Note] InnoDB: Using Linux native AIO mariadb | 2017-04-04 8:29:00 140557637724096 [Note] InnoDB: Using SSE crc32 instructions mariadb | 2017-04-04 8:29:00 140557637724096 [Note] InnoDB: Initializing buffer pool, size = 256.0M mariadb | 2017-04-04 8:29:00 140557637724096 [Note] InnoDB: Completed initialization of buffer pool mariadb | 2017-04-04 8:29:00 140557637724096 [ERROR] InnoDB: auto-extending data file ./ibdata1 is of a different size 0 pages (rounded down to MB) than specified in the .cnf file: initial 768 pages, max 0 (relevant if non-zero) pages! mariadb | 2017-04-04 8:29:00 140557637724096 [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! mariadb | 2017-04-04 8:29:00 140557637724096 [ERROR] Plugin 'InnoDB' init function returned error. mariadb | 2017-04-04 8:29:00 140557637724096 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. mariadb | 2017-04-04 8:29:00 140557637724096 [Note] Plugin 'FEEDBACK' is disabled. mariadb | 2017-04-04 8:29:00 140557637724096 [ERROR] Could not open mysql.plugin table. Some plugins may be not loaded mariadb | 2017-04-04 8:29:00 140557637724096 [ERROR] Unknown/unsupported storage engine: InnoDB mariadb | 2017-04-04 8:29:00 140557637724096 [ERROR] Aborting mariadb | mariadb exited with code 1después de ejecutar mi directorio ./mysql1/ y se creó el subarchivo:
C:\USERS\--------\DOCUMENTS\DOCKER\MARIADB\MYSQL1 | aria_log.00000001 | aria_log_control | ibdata1 | \---mysqlSí, sé que se trata de mis volúmenes (algo sobre permisos o acceso o ...) No tengo idea de cómo resolverlo.
Estaba experimentando el mismo problema y la única forma de resolverlo era eliminar la carpeta MARIADB\MYSQL1. Sí, perdí todos los registros de la base de datos de todos mis sitios de desarrollo, pero para mí, toda era información de prueba de todos modos, por lo que no se perdieron datos reales.
Después de eliminar la carpeta MYSQL1, ejecuté:
docker-compose build --no-cache MariaDBLuego puse en marcha el contenedor:
docker-compose up -d mariadbEl error finalmente desapareció y pude usar mi contenedor MariaDB nuevamente. ¡Espero que esto ayude a alguien en el futuro!