-
Notifications
You must be signed in to change notification settings - Fork 702
Unable to run s2i after MacOS update (10.12.2) #666
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
Comments
Ahmeds-MBP-2:~ aelmadhoun$ s2i build https://github.com/openshift/django-ex centos/python-35-centos7 hello-pytho2 --loglevel=3 | tee log2.txt goroutine 1 [running]: goroutine 5 [chan receive]: goroutine 6 [syscall]: goroutine 18 [select]: goroutine 10 [select]: goroutine 11 [select]: goroutine 34 [IO wait]: goroutine 16 [IO wait]: goroutine 49 [select]: |
@csrwng can you see if you can recreate this either w/ the latest release, or w/ the code in master? we may just need to do a new release. |
I am running MacOS Sierra (10.12.2)
My guess is that this is an issue with either docker, docker-machine, or docker-machine-driver-xhyve. Please try updating them to the latest version. You'll need to re-create your docker-machine so it picks up the latest docker image. |
I have re-installed MacOS Sierra in case my install went bad, and I have re-installed all the same versions of docker, docker-machine and docker-machine-driver-xhyve (homebrew), I also removed the $HOME/.docker and re-created a brand new VM (Virtualbox & Xhyve), both run into an exception. I am attaching a copy of the trace logs in case anyone may have an insight into what is going on. I also believe the issue is in downloading the image only, as I was able to run the same docker image (on same docker-machine/xhyve VM/same docker image) and it works. After I manually downloaded the image, I was able to run s2i given the image was previously downloaded. Do you think there is any sort of library update that I am missing, any pointer would really be helpful as I think there is something in the way s2i downloads the image that is causing the segmentation fault. |
@aelmadho Ahh I see ... the issue is the execution context during the pull timing out and causing the go panic. We should not have a timeout for a pull. This is not a Mac specific issue. It has to do with the time it takes to perform the docker operation. Let me take a look and see if this has been fixed recently. |
It's still an issue, I'll submit a fix. |
Thank you @csrwng, we all appreciate your support. |
@jim-minter just fyi ... my theory was that the pull was taking longer than the timeout and that somehow the code was proceeding without the pull having completed. However, earlier today I had a chance to test that theory and was not able to reproduce. Bottom line is that I still don't know why the panic is happening. It could be completely unrelated to the pull. |
The latest s2i release we published (1.1.3) is compiled using Go 1.6, which does not support MacOS Sierra. This is resolved in Go 1.7.1. golang/go#16570 @aelmadho are you able to compile master for yourself using latest 1.7 and see if you still have the issue? @bparees we will surely need to spin a new s2i release, but I suggest hanging fire on it until we know if master works for the reporter. |
(edited previous comment: Go 1.6 does not support MacOS Sierra, period.) |
@aelmadho if you're able to test (and don't want to compile it yourself) I've put a build at https://gist.github.com/jim-minter/3247c647bbcf2eef11320e4961a739c5/raw/65f2fa2742e0a8fa93d44fda1395015b4119d8fc/source-to-image-v1.1.3-83-g74ab5f1-74ab5f1-darwin-amd64.tar.gz - feedback is welcome. |
@bparees please will you spin a new s2i release using 1.7.x? |
@bparees thanks |
Running with docker-machine and xhyve driver, I am no longer able to run s2i:
s2i build https://github.com/openshift/django-ex centos/python-35-centos7 hello-pytho2
The text was updated successfully, but these errors were encountered: