Dear all ,
I am following the guide on
https://github.com/apetkau/galaxy-hackathon-2014/tree/master/smalt to test the
smalt docker integration tutorial.
The SMALT within docker on my local Galaxy sometimes works well as follow:
502 7789 0.0 0.0 271680 6236 ? Sl 21:42 0:00
/usr/bin/docker run -e GALAXY_SLOTS=1 -v
/data/Docker/galaxy-dist:/data/Docker/galaxy-dist:ro -v
/data/Docker/galaxy-dist/tools/docker:/data/Docker/galaxy-dist/tools/docker:ro
-v
/data/Docker/galaxy-dist/database/job_working_directory/000/82:/data/Docker/galaxy-dist/database/job_working_directory/000/82:rw
-v
/data/Docker/galaxy-dist/database/files:/data/Docker/galaxy-dist/database/files:rw
-v
/data/Docker/galaxy-dist/database/files:/data/Docker/galaxy-dist/database/files:rw
-w /data/Docker/galaxy-dist/database/job_working_directory/000/82 --net none
smalt-galaxy:shenweiyan
/data/Docker/galaxy-dist/database/job_working_directory/000/82/container.sh
But sometimes it failed with the error:
setup mount namespace bind mounts Creating new bind-mount target, mkdir
/var/lib/docker/devicemapper/mnt/405781730f76d0f3d08eb86e8e14448c47914e727508224f9c70a1ae72cf302b/rootfs/data/Docker/galaxy-dist/database/files::
read-only file system2014/11/14 21:28:13 Error response from daemon: Cannot
start container
405781730f76d0f3d08eb86e8e14448c47914e727508224f9c70a1ae72cf302b: setup mount
namespace bind mounts Creating new bind-mount target, mkdir
/var/lib/docker/devicemapper/mnt/405781730f76d0f3d08eb86e8e14448c47914e727508224f9c70a1ae72cf302b/rootfs/data/Docker/galaxy-dist/database/files::
read-only file systemIt seems that docker running with sudoer
unsteadily.Any idear how do I fix it?
Kind regards,
weiyan
___________________________________________________________
Please keep all replies on the list by using "reply all"
in your mail client. To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
http://lists.bx.psu.edu/
To search Galaxy mailing lists use the unified search at:
http://galaxyproject.org/search/mailinglists/
