Closed rapejim closed 5 years ago
Thanks for reporting this issue. I'll have a look 👍
Hm ... I just did a docker pull and was successfully able to run the app with the latest image. Of course in the meantime the latest image changed (as I merged some stuff) so maybe you can give it a try again please?
In case it is still not working then I'd like to ask you to provide a few additional things:
I tried a few minutes ago pulling the last image from docker hub and have the same errors, I write you here the required info:
Thanks for providing the details. I just started a fresh Ubuntu 18.04 VM and installed the latest docker version. Again I was able to successfully pull the latest image and just run it without any of those errors.
Could you try something please? My app uses the official ruby:2.6.5-alpine
base image.
Can you check if this is working for you:
docker run -it ruby:2.6.5-alpine ruby -e "puts 'Hello World'"
Just to see if it maybe is related to the base image and does not just pop up on my application.
Note: Maybe related: https://github.com/sass/sassc-ruby/issues/146
The same problem for me. It worked before.
After "docker pull" the latest image do not work with the same error message.
Turn docker on Ubuntu 16.04.
"Hello world" works without problem :
~> docker run -it ruby:2.6.5-alpine ruby -e "puts 'Hello World'"
Unable to find image 'ruby:2.6.5-alpine' locally
2.6.5-alpine: Pulling from library/ruby
9d48c3bd43c5: Already exists
9ce9598067e7: Already exists
278f4c997324: Already exists
867dd521f6d0: Already exists
c69cba5b7867: Already exists
Digest: sha256:3e6d5cb132e88fe125ab40cb31db200ef9b953f21a5e0cfc0d88ba835ba4a51b
Status: Downloaded newer image for ruby:2.6.5-alpine
Hello World
@paulz1 thanks for commenting and testing.
Since I'm unable to reproduce the issue on the machines I have access to it was only possible to do a blind change (#239) based on a comment in https://github.com/sass/sassc-ruby/issues/146 which could fix the issue.
Can you please give it a try with this image:
docker pull klausmeyer/docker-registry-browser:test-for-issue-230
Also @rapejim could give it a try. In case this is working for you guys I can merge it to master
branch to make it available in the latest
tag.
Thank you, Klaus, for replying and helping.
Just tested with docker-registry-browser:test-for-issue-230 image and it works perfectly. So you probably found the solution.
Nice :tada:
Change is merged. Will be available as latest
tag soon.
I'm sorry, I couldn't test it before. But now it's working perfectly with the latest image!!!
No worries. Thanks for the update 👍
I have recreated a container with de latest image (updated 4 hours ago on docker hub): And don't run never ok, have a ruby errors:
But with the image of version 1.2.3 (updated 2 months ago on docker hub), works perfectly.