Hi Diana, This is a known bug that's in swarm.
I'll be looking into this soon. Tim > On Sep 25, 2015, at 3:32 AM, Diana J Arroyo <darr...@us.ibm.com> wrote: > > Hi, > I'm getting "ERRO[0038] HTTP error: no resources available to schedule > container status=500" when trying to deploy a container through the swarm > manager framework running on Mesos. > > Here are some details: > mesos version: 0.23.0 > swarm version: 0.4.0 > > command used to start mesos master... > HOST1<'mesos' userid>: ./bin/mesos-master.sh --ip=x.x.x.1 > --work_dir=/var/lib/mesos --log_dir=../log_dir --quiet > > commands used to start mesos node agent... > HOST2<'mesos' userid>: export DOCKER_HOST=0.0.0.0:2375 > HOST2<'mesos' userid>: ./bin/mesos-slave.sh --containerizers=docker,mesos > --executor_registration_timeout=5mins --master=x.x.x.1:5050 > --log_dir=../log_dir > > command used to start swarm master... > HOST1<'mesos' user>: /root/gocode/bin/swarm --debug manage -c > mesos-experimental --cluster-opt mesos.address=x.x.x.1 --cluster-opt > mesos.port=3375 --host x.x.x.1:4375 x.x.x.1:5050 > > command used to create a container... > HOST1<'root' user>:docker -H tcp://x.x.x.1:4375 run -d -c 2 --name sleep > ubuntu /bin/sleep 1000000000 > > error message displayed on the swarm console... > HOST1<swarm console>: ERRO[0038] HTTP error: no resources available to > schedule container status=500 > > error message from tmp directory... > HOST2<'/tmp' directory>: > cat > mesos/slaves/.../frameworks/.../executors/sleep.c10c3f7af11e/runs/2d349f82-4927-4c63-82e0-c8eaf34362fd/stderr > I0925 04:39:25.770843 17606 exec.cpp:132] Version: 0.23.0 > I0925 04:39:25.782850 17627 exec.cpp:206] Executor registered on slave > 20150925-034538-4226419721-5050-19580-S5 > Post > http:///var/run/docker.sock/v1.19/containers/create?name=mesos-20150925-034538-4226419721-5050-19580-S5.2d349f82-4927-4c63-82e0-c8eaf34362fd: > dial unix /var/run/docker.sock: no such file or directory. Are you trying to > connect to a TLS-enabled daemon without TLS? > W0925 04:39:25.782850 17620 logging.cpp:81] RAW: Received signal SIGTERM from > process 17511 of user 1000; exiting > > error message from mesos log... > HOST2: > cat ~/mesos-0.23.0/log_dir/lt-mesos-slave.ERROR > Log file created at: 2015/09/25 04:39:31 > Running on machine: mesosStagingCompute9 > Log line format: [IWEF]mmdd hh:mm:ss.uuuuuu threadid file:line] msg > E0925 04:39:31.302273 17540 slave.cpp:2821] Failed to update resources for > container 2d349f82-4927-4c63-82e0-c8eaf34362fd of executor sleep.c10c3f7af11e > running task sleep.c10c3f7af11e on status update for terminal task, > destroying container: Failed to 'docker inspect > mesos-20150925-034538-4226419721-5050-19580-S5.2d349f82-4927-4c63-82e0-c8eaf34362fd': > exit status = exited with status 1 stderr = Error: No such image or > container: > mesos-20150925-034538-4226419721-5050-19580-S5.2d349f82-4927-4c63-82e0-c8eaf34362fd > > > The error message from the tmp directory looks like the DOCKER_HOST env. var > is not being picked up since I get this similar error message on HOST2 when I > do a simple 'docker ps' instead of 'docker -H 0.0.0.0:2375 ps'. > > Is there any other configuration I need to setup on the slave such that the > slave can create a container using the Mesos and Swarm environment? Please > advise. > > Best Regards, > Diana Arroyo > darr...@us.ibm.com >
