<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">You’re right, thanks very much! <div class=""><br class=""></div><div class="">Submitting the job `qsub -b y -cwd id` produces: </div><div class="">uid=1001(sgeadmin) gid=1001(sgeadmin) groups=1001(sgeadmin),20000</div><div class=""><br class=""></div><div class="">Strangely, however, executing the same command on the same node with ssh yields a different result:</div><div class=""><div class="">sgeadmin@master:~$ ssh node001 id</div><div class="">uid=1001(sgeadmin) gid=1001(sgeadmin) groups=1001(sgeadmin),999(docker)</div></div><div class=""><br class=""></div><div class="">This explains the discrepancy I’m seeing. Why does qsub get a uid 1001 without docker while ssh gets a uid 1001 with docker? </div><div class=""><br class=""></div><div class="">My first thought to resolve this was to `usermod` the sgeadmin user on my AMI to add the docker group to it, but I realize there is no sgeadmin user on my AMI. It’s created by starcluster on node boot. </div><div class=""><br class=""></div><div class="">How can this be set? </div><div class=""><br class=""></div><div class="">Thanks,</div><div class="">Xander</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Nov 16, 2015, at 19:26, Rayson Ho <<a href="mailto:raysonlogin@gmail.com" class="">raysonlogin@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Xander,<br class=""><br class="">Can you check whether the Grid Engine job environment has the "docker" group as one of the supplemental groups by submitting a job that runs "id"?<br class=""><br class=""><a href="http://man7.org/linux/man-pages/man1/id.1.html" class="">http://man7.org/linux/man-pages/man1/id.1.html</a><br class=""><br class="">IIRC, Docker requires the process to be a member of the docker group in order to dial <span style="font-size:12.8px" class=""> /var/run/docker.sock.</span><br class=""><br class="">Rayson<br class=""><br class="">==================================================<br class="">Open Grid Scheduler - The Official Open Source Grid Engine<br class=""><a href="http://gridscheduler.sourceforge.net/" class="">http://gridscheduler.sourceforge.net/</a><br class=""><a href="http://gridscheduler.sourceforge.net/GridEngine/GridEngineCloud.html" class="">http://gridscheduler.sourceforge.net/GridEngine/GridEngineCloud.html</a><br class=""><br class=""><br class=""><br class=""><br class="">On Mon, Nov 16, 2015 at 7:15 PM, Xander Dunn <<a href="mailto:xander.dunn@icloud.com" class="">xander.dunn@icloud.com</a>> wrote:<br class="">><br class="">> I have star cluster installed from the develop branch because I need to use c4 instance types, which aren’t in a released version yet. I have open grid scheduler 2011.11 installed on an Ubuntu 14.04 AMI.<br class="">><br class="">> I have Docker installed in that AMI and the daemon starts on boot. If I manually ssh into my master node or any worker node and execute a Docker command, it works. The Docker daemon is found and the command succeeds. Furthermore, executing any docker command from the master node in the form `ssh node001 docker pull IMAGE` also works correctly.<br class="">><br class="">> However, those same commands, when executed with qsub, will fail because the running Docker daemon can’t be found:<br class="">> Post IMAGE: dial unix /var/run/docker.sock: permission denied.<br class="">> * Are you trying to connect to a TLS-enabled daemon without TLS?<br class="">> * Is your docker daemon up and running?<br class="">><br class="">> Example: `qsub -V -b y -cwd docker pull ubuntu:14.04`<br class="">><br class="">> What’s the difference in the way qsub executes commands that’s causing this?<br class="">><br class="">> Thanks,<br class="">> Xander<br class="">> _______________________________________________<br class="">> StarCluster mailing list<br class="">> <a href="mailto:StarCluster@mit.edu" class="">StarCluster@mit.edu</a><br class="">> <a href="http://mailman.mit.edu/mailman/listinfo/starcluster" class="">http://mailman.mit.edu/mailman/listinfo/starcluster</a></div>
</div></blockquote></div><br class=""></div></body></html>