Date: Fri, 23 Oct 2015 13:27:04 -0500 From: Joseph Love <joe@getsomewhere.net> To: freebsd-virtualization@freebsd.org Subject: some Docker cmd options not working? Message-ID: <0DBFBC10-4B04-4664-9EEE-26592B9C41DE@getsomewhere.net>
next in thread | raw e-mail | index | archive | help
Hi, I=E2=80=99ve been poking at using docker to run some linux apps. In = doing so, I=E2=80=99ve been looking at a couple features that I cannot = tell if they=E2=80=99re failing, or just not implemented, or if = there=E2=80=99s some other reason that it isn=E2=80=99t working. The two options I=E2=80=99ve tried sofar that haven=E2=80=99t seemed to = have any effect are these -v & -u. eg: docker run -i -v /tmp:/mnt =E2=80=94name=3Dtest centos docker exec -u testuser test /bin/sh I=E2=80=99ve been using the centos docker image as a basis for trying a = few things, so the paths used in the -v command exist, both the path = specified for the host, as well as that for the jailed guest. In the = case of the user flag, -u, the user definitely exists in the guest. If = I run a program which will run for a bit, and check the hosts=E2=80=99s = =E2=80=9Cps aux=E2=80=9D list, the user it runs as is root, rather than = the user/userid I specified. I=E2=80=99m mostly just curious if these parameters aren=E2=80=99t = implemented, or if I=E2=80=99m trying something wrong. Thanks, -Joe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0DBFBC10-4B04-4664-9EEE-26592B9C41DE>