Docker GUI plugin now stable

I need a clean docker container with ubuntu to compile and run airdcnano.

I pull the ubuntu image, run the container allright
but when I try to docker attach to it so I can install gcc etc
nothing happens.
I get no prompt, just a blinking cursor and no ctrl-q ctrl-p ctrl-x works, I have to kill the ssh session.

I also get nothing when trying to run ls through the plugin gui.

What am I doing wrong?

Nothing, it just takes me back to my prompt without doing nothing...

I'm assuming you've tried to just hit enter after attaching? Attaching won't necessarily generate any output right away, you might have to kick the shell.

docker ps -a shows the container running.
I've pressed enter and any other combination, nothing works, not even ctrl-z

weird thing is the gui run command button doesn't work either.
I enter ls -la /opt and press start, and I only get a screen flash like a refresh but no output...

time="2016-01-04T18:05:11.614923131+02:00" level=info msg="GET /v1.21/containers/airdc/json"
time="2016-01-04T18:05:11.617251657+02:00" level=info msg="POST /v1.21/containers/airdc/attach?stderr=1&stdout=1&stream=1"
time="2016-01-04T18:05:29.605089795+02:00" level=warning msg="Your kernel does not support OOM notifications: There is no path for \"memory\" in state"
time="2016-01-04T18:05:29.643789878+02:00" level=info msg="GET /v1.21/containers/airdc/json"

Can you try to start your container manually rather than through the GUI? I'm not sure if they have any sort of entrypoint. I don't think they're meant to be run directly but rather have images created off of them? When you run the image, are you giving it any sort of entrypoint in the GUI? You should be able to specify one in the "Extra Arguments" section:

--entrypoint=/bin/bash

You should then be able to attach. Also, you may want to look into creating a Dockerfile instead of manually updating the image as it's a lot easier to update/maintain the image that way.

time="2016-01-04T20:09:08.040370682+02:00" level=error msg="Error running command in existing container fa7b71ae8798a46ac67705bc8b2f3f43fb77865378f9067a5fc9105851029105: No active container exists with ID fa7b71ae8798a46ac67705bc8b2f3f43fb77865378f9067a5fc9105851029105"
time="2016-01-04T20:09:08.040449179+02:00" level=error msg="Error running exec in container: execcantrun: Cannot run exec command 777a7cc0bbe45f70538b0ce647dddc116126a36053425032f3bd67a4d236240d in container fa7b71ae8798a46ac67705bc8b2f3f43fb77865378f9067a5fc9105851029105: No active container exists with ID fa7b71ae8798a46ac67705bc8b2f3f43fb77865378f9067a5fc9105851029105\n"

I also tried the entrypoint with no luck...

What I want to do is install gcc and build dependencies, compile and install airdcnano and then save/export that image for later use/share...
Maybe I should remove the plugin and go manually all the way...???

You can create a Dockerfile similar to the following:

FROM ubuntu:latest


MAINTAINER Your Name <you@domain.com>


ENV DEBIAN_FRONTEND noninteractive


# Install the toolchain and dependencies
RUN apt-get install build-essential libbz2-dev libncursesw5-dev scons zlib1g-dev libglib2.0-dev libssl-dev libstdc++6 libminiupnpc-dev libnatpmp-dev libtbb-dev libgeoip-dev libboost1.55-dev libboost-regex1.55-dev libboost-thread1.55-dev libboost-signals1.55-dev libboost-system1.55-dev libleveldb-dev git


# Clone and build airdcano
RUN mkdir /source; cd /source; git clone https://github.com/airdcnano/airdcnano.git; cd airdcnano; scons -j2; scons install


ENTRYPOINT /usr/local/bin/airdcnano

That's an example, it probably isn't complete. You can build the container with `docker build -t yourname/airdcnano` in the directory containing the Dockerfile. It may be worthwhile to put the last RUN command into a script instead, I would read the Dockerfile documentation.

However. It looks like airdcnano is a GUI app, or are you trying to use it's text mode?

When I download emby/embyserver from the repo and run it, the container run command runs ok but still no attach... wtf?

Airdc is gui and airdcnano is the linux terminal implementation...

Could you check the precise arguments used to start Docker? Just run "ps aux | grep docker" and see if you can find the one you're trying to run.

I will check on what you said later on. Right now I'm in the process of...

$docker pull ubuntu
$docker run -i -t ubuntu /bin/bash
#apt-get install git gcc g++ etc...
#git clone airdcnano in /sources/
#scons -j2 in /sources/airdcnano

after i check that airdc runs ok then I will
$docker commit container airdcnano

and will try to use that image via the gui...

root@tank:~# ps aux | grep docker
root 12094 0.9 0.6 753900 25464 ? Sl 17:59 1:53 /usr/bin/docker daemon -p /var/run/docker.pid -H unix:///var/run/docker.sock -H tcp://127.0.0.1:42005
root 17761 0.0 0.0 8036 2108 pts/2 S+ 21:16 0:00 grep docker
root@tank:~#

That would imply that the container isn't actually running?

root@tank:~# docker commit elegant_pike airdcnano
7ea07b10fa36ce97a6326fdb4f5c1a520cfd560b92e19e873a2d93d17ca6c853
root@tank:~# docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
b8e0ef845d01 ubuntu "/bin/bash" 53 minutes ago Exited (2) About a minute ago elegant_pike
root@tank:~#

and I also managed to attach to that container...

`docker ps -a` doesn't tell you the command line options passed to "docker" to start the container.