search

ContainerSolutions / minimesos

The experimentation and testing tool for Apache Mesos - NO LONGER MAINTANED!
https://www.minimesos.org
Apache License 2.0
427 stars 61 forks source link

Minimesos fails to start on AWS because of unmounted cpu subsystem #295

Closed frankscholten closed 8 years ago

frankscholten commented 8 years ago

Running a t2.medium instance with AMI amzn-ami-hvm-2015.09.2.x86_64-gp2 (ami-e1398992)

[ec2-user@ip-172-31-20-243 ~]$ minimesos up

Container [minimesos-agent-1252917103-2490883436] did not start within 60 seconds.
STDERR: WARNING: Logging before InitGoogleLogging() is written to STDERR
STDERR: I0314 11:04:08.973601 23240 process.cpp:995] libprocess is initialized on 172.17.0.9:5051 for 8 cpus
STDERR: I0314 11:04:08.973839 23240 logging.cpp:172] INFO level logging started!
STDERR: I0314 11:04:08.974129 23240 logging.cpp:177] Logging to /var/log
STDERR: I0314 11:04:08.974169 23240 main.cpp:185] Build: 2015-10-12 20:57:28 by root
STDERR: I0314 11:04:08.974195 23240 main.cpp:187] Version: 0.25.0
STDERR: I0314 11:04:08.974236 23240 main.cpp:190] Git tag: 0.25.0
STDERR: I0314 11:04:08.974261 23240 main.cpp:194] Git SHA: 2dd7f7ee115fe00b8e098b0a10762a4fa8f4600f
STDERR: Failed to create a containerizer: Could not create DockerContainerizer: Failed to create docker: Failed to find a mounted cgroups hierarchy for the 'cpu' subsystem; you probably need to mount cgroups manually
[ec2-user@ip-172-31-20-243 ~]$
frankscholten commented 8 years ago

Fixed when using Ubuntu 14.04 with AMI ami-47a23a30