Hi, I’m not sure if this is the right place.
Currently I’m creating an Image and login to the Container in two ways. I’m having problems with both ways and I’m not sure how I should do it “right”.
I’m running Ubuntu 15.10 (Host), Docker 10 and prepared an Ubuntu 14.04 LTS image, since I want to develop a BSP with an older Buildroot '14 Buildsystem. The image I tagged v0.0.101. I’m behind a proxy. Host has valid proxy settings, which I copied into the /etc/environment (image). Ping and DNS resolution are working on host. In the image I created user “myuser” who also exists on host.
Variation A )
$ docker run -ti ubuntu-14.04:0.0.101 su myuser
Running it like this allows me to go into buildroot, and build the specified defconfig. Buildroot downloads packages, and runs them until a package e.g. gettext which checks if a working “fork()” call. This seems to fork the su “myuser” into the child call, forks out the parent which ends immediately and thus I’ll find myself outside with the host’s prompt. The container stopped. I assume child process is killed, since parent ended. I never achieve to run buildroot further then to this package with the specified fork()-test.
Variation B )
$ docker run --user myuser -ti ubuntu-14.04:0.0.101 /bin/bash
fork() now is not a problem, but no further packages can be downloaded. Ping works, but wget fails. I somehow quickfixed this by executing inside the container “su myuser” which solves the problem. Somehow I seem to be logged in to the specified user, but the environment is not set correctly.
What would be the correct way for me to run an image and create a container?