[MDEV-15882] Error starting MariaDB Server 10.2.14 within Docker with mounted volume Created: 2018-04-16  Updated: 2018-07-18  Resolved: 2018-07-18

Status: Closed
Project: MariaDB Server
Component/s: Configuration
Affects Version/s: 10.2.14
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Rick Tuk Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-16015 Unhandled EOPNOTSUPP of posix_falloca... Closed

 Description   

Docker container running MariaDB Server with /source/mariadb mounted using --mount type=bind,src=~/docker/test,dst=/source results in an error creating the ibdata1 file
When running without a mount the error does not show up

Installing MariaDB/MySQL system tables in '/source/mariadb' ...
 
2018-04-16 14:18:04 140365721791368 [ERROR] InnoDB: preallocating 10485760 bytes for file /source/mariadb/ibdata1 failed with error 95
 
2018-04-16 14:18:04 140365721791368 [ERROR] InnoDB: Could not set the file size of '/source/mariadb/ibdata1'. Probably out of disk space
 
2018-04-16 14:18:04 140365721791368 [ERROR] InnoDB: Database creation was aborted with error Generic error. You may need to delete the ibdata1 file before trying to start up again.
 
2018-04-16 14:18:05 140365721791368 [ERROR] Plugin 'InnoDB' init function returned error.
 
2018-04-16 14:18:05 140365721791368 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
 
2018-04-16 14:18:05 140365721791368 [ERROR] Unknown/unsupported storage engine: InnoDB
 
2018-04-16 14:18:05 140365721791368 [ERROR] Aborting

Docker information:

Containers: 11
 
 Running: 0
 
 Paused: 0
 
 Stopped: 11
 
Images: 109
 
Server Version: 18.03.0-ce
 
Storage Driver: overlay2
 
 Backing Filesystem: extfs
 
 Supports d_type: true
 
 Native Overlay Diff: true
 
Logging Driver: json-file
 
Cgroup Driver: cgroupfs
 
Plugins:
 
 Volume: local
 
 Network: bridge host ipvlan macvlan null overlay
 
 Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
 
Swarm: active
 
 NodeID: tweirfbybrhaez0cq1dhoruni
 
 Is Manager: true
 
 ClusterID: ge4etfk2nss80dbjrtrcjibi4
 
 Managers: 1
 
 Nodes: 1
 
 Orchestration:
 
  Task History Retention Limit: 5
 
 Raft:
 
  Snapshot Interval: 10000
 
  Number of Old Snapshots to Retain: 0
 
  Heartbeat Tick: 1
 
  Election Tick: 3
 
 Dispatcher:
 
  Heartbeat Period: 5 seconds
 
 CA Configuration:
 
  Expiry Duration: 3 months
 
  Force Rotate: 0
 
 Autolock Managers: false
 
 Root Rotation In Progress: false
 
 Node Address: 192.168.65.3
 
 Manager Addresses:
 
  192.168.65.3:2377
 
Runtimes: runc
 
Default Runtime: runc
 
Init Binary: docker-init
 
containerd version: cfd04396dc68220d1cecbe686a6cc3aa5ce3667c
 
runc version: 4fc53a81fb7c994640722ac585fa9ca548971871
 
init version: 949e6fa
 
Security Options:
 
 seccomp
 
  Profile: default
 
Kernel Version: 4.9.87-linuxkit-aufs
 
Operating System: Docker for Mac
 
OSType: linux
 
Architecture: x86_64
 
CPUs: 4
 
Total Memory: 3.855GiB
 
Name: linuxkit-025000000001
 
ID: VREV:IY4P:RYPO:TDNF:MY3R:OWL2:4MWZ:3H3R:WGTJ:6X62:ACUN:536N
 
Docker Root Dir: /var/lib/docker
 
Debug Mode (client): false
 
Debug Mode (server): true
 
 File Descriptors: 37
 
 Goroutines: 159
 
 System Time: 2018-04-16T12:32:46.6580421Z
 
 EventsListeners: 2
 
HTTP Proxy: docker.for.mac.http.internal:3128
 
HTTPS Proxy: docker.for.mac.http.internal:3129
 
Registry: https://index.docker.io/v1/
 
Labels:
 
Experimental: true
 
Insecure Registries:
 
 127.0.0.0/8
 
Live Restore Enabled: false



 Comments   
Comment by Elena Stepanova [ 2018-07-18 ]

Thanks for the report.
While this entry was created earlier and thus should be considered original, there is already an ongoing discussion in MDEV-16015, which seems to be the same problem. So, unless you have objections, I suggest to continue tracking the issue there.

Generated at Thu Feb 08 08:24:44 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.