search

jhipster / jhipster-docker

DO NOT USE - DEPRECATED REPO - Old jdubois/jhipster Docker image, replaced by https://hub.docker.com/r/jhipster/jhipster/
Other
59 stars 38 forks source link

Connection to localhost closed. #1

Closed wowczarczyk closed 10 years ago

wowczarczyk commented 10 years ago

I was following the docker tutorial and shorty after executing this step:

ssh -p 4022 jhipster@localhost

I get:

root@main:~# ssh -p 4022 jhipster@localhost
jhipster@localhost's password:
Welcome to Ubuntu 14.04 LTS (GNU/Linux 3.13-0.bpo.1-amd64 x86_64)

 * Documentation:  https://help.ubuntu.com/
Connection to localhost closed.

For some reason the SSH connection is immediately closed

Andy-11 commented 10 years ago

I've run into the same issue. Did you manage to get round it voodoorider?

Cheers

wowczarczyk commented 10 years ago

No, unfortunately not. I started using jhipster installed directly on OS without Docker at all. Pretty unfortunate...

Andy-11 commented 10 years ago

Thanks, I'm wondering if it's because my Ubuntu version is only 12.04 instead of 14.04. Might fire up a new VM to try later.

awaddell commented 10 years ago

I had the same issue and, seeing the aborted docker shell reported 14.04 while the host is 12.04, I upgraded my existing host and this fixed it with no complications.

http://ubuntuserverguide.com/2014/06/how-to-upgrade-ubuntu-server-12-04-to-ubuntu-server-14-04-lts.html

post upgrade: Docker version 1.1.2, build d84a070

jdubois commented 10 years ago

Thanks @awaddell I didn't know how to reproduce this. So you need te have the same Ubuntu version for the host and the container... Talk to me again about container portability...

awaddell commented 10 years ago

@jdubois I speculated that having a future version of Ubuntu in the container might be the cause of this particular problem but I wouldn't rush to assume the same of an older version or that they need to be the same version.

I can see that I installed docker 1.1.2 on August 4th so the docker version has not changed.

I was running kernel version 3.8.0-44-generic with 12.04LTS and am now running 3.13.0-35-generic with 14.04LTS

This thread: http://stackoverflow.com/questions/24217566/for-docker-will-apps-stop-working-when-host-kernel-is-updated

says:

"Should major updates to the libc happen, this library is not shared between the host and the containers, it is embedded in your container anyway."

And (I think) that should be all that sshd/bash/sh need.

I've had a look around for core dumps or logs but the logging is very spartan.

Can I suggest you leave the default Ubuntu 14.04LTS logging as is or at least allow to retain some logging? I can't see beyond my most recent boot so visibility to the issue is gone.

Also, might be an idea to disable apparmor for this demo project as apparmor is up there in the list of suspects.

Thanks for the project!

jdubois commented 10 years ago

@awaddell thanks for the feedback. We will need to have a look at apparmor (cc @jmirc )