-
Notifications
You must be signed in to change notification settings - Fork 192
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vulnerable #1
Comments
Thanks for reporting! It should be meter of base image, in this case i've used official Ubuntu ones. Those images are fixed and updated yesterday, according this issue, which should automatically trigger fresh build of this repo. Can you try to pull newest version of |
Thanks for the reply! That's exactly what I thought, but it didn't work earlier. For the record, I'm doing:
And I get:
This is most probably due to me doing something wrong or the upstream image. Not ubuntu-sshd. But anyone is welcome to help me :) |
You're mentioning Btw make sure that you're running 12.04 or 14.04 (latest) tag, There is some issues with building 13.10 12.10 and 13.04 tags. I'll inspect them later today. |
docker_sshd is the name I give it (in the docker run command). I tried changing it, to make sure I'm using a recent image, but still getting 6.6. Using 14.04. |
I found the culprit! I was using the 14.04 tag. Changing to "latest" fixed it! |
Tnx for the info. I'll definitely give more attention to this project in the short future, to add new versions and check situation with older ones. |
Great docker.
But it still uses libc 2.19-0ubuntu6.6, which is vulnerable. I made a fresh install but it still uses that version. Do you think it's a matter of Dockerfile?
Source
The text was updated successfully, but these errors were encountered: