Github for mac version is too old
Already on GitHub? Sign in to your account. As reported in our troubleshooting wiki , for Mac OS X The diagnosis for this is to try to do a git init it'll fail.
- Install old version of Homebrew on Snow Leopard - Ask Different.
- Frequently Asked Questions!
- connect to smb server mac os x!
The only solution seems to be to download Xcode apparently, the error is because some libraries are missing and only get installed with Xcode. But today, we found that Apple removed the proper Xcode version from the Apple Store. Now the only fix is to go to the Apple Developer website and search for the the right Xcode there. This requires an Apple Developer account that the students probably won't have.
Visual Studio for Mac version Release Notes | Microsoft Docs
I was teaching while iglpdc and mckays were dealing with the git installation problems but I believe the installer from sourceforge no longer work? If you download the appropriate installer, "Snow Leopard" for Out of curiosity, were you trying to use the installers for the most recent version of git when using the git-osx-installers? I will ask around at PyCon if we can set up easily test envs for the different OSX versions and installs.
I've been looking at doing this for OpenHatch anyway. If anyone has additional details to add, especially which version of Git was giving the "Lazy symbol" error, that would probably be helpful to add either here or there. Thanks jiffyclub.
Install Docker Compose
Our setup instructions  already link to the correct installer for each version. Also, I found the problem pretty much in any workshop I taught in the last 6 months I'm almost sure to say that is Having said that, I didn't actually check that the students were using the correct installer, so it maybe the problem gets fixed now if you use the correct installer, and we were just fixing it in the wrong way by installing Xcode.
Actually, this particular student in the last workshop didn't seem much aware of which version she was using. To fix this, I'm making two changes:. This brings me to eddelbuettel 's point. There are many reasons for having an outdated OS at our workshops: some students borrow one; some others get one at work, but they don't have admin rights; some have very old laptops that cannot be updated, and most don't think it is necessary.
This girl had a very strong point: she bought her laptop a little over a year ago so "it was brand new" so "why update something new".
- raspberry pi xbmc tutorial mac.
- how to open cd files on mac;
- Features & interface?
- do you need to defrag mac hard drive!
- download youtube videos to itunes free mac?
- mosaico de fotos gratis mac;
As far as for Docker, I think it cannot beat our current setup, at least in simplicity for a novice learner. I agree with the suggestion on how to check OS version, which installer to choose, how to install xcode command line tools if needed to the setup instructions for OS X.
My overall view is that checking the OS X version pre setup would minimize the setup frustration for users. The burden shouldn't be on the student or workshop helpers to guess what might work.
Honestly, I dread the set up portion of any workshop SWC or otherwise. I think that it may be helpful for testing the setup instructions. Most of the issues had to do with getting the IPs set correctly since boot2docker runs a VM, getting ssh to work properly, and permissions.
Had that too when I once ran, just as a test, boot2docker on my work pc to serve the RStudio Server container: that worked like a charm and stayed up for several months once I knew what the address was. But all suggestions have issues and nothing dominates so we're back to individual preferences.
I think it is a great solution for many development and deployment problems. This would put the burden of finishing the setup on our instructors and many of us are also fairly new to the VM world. It maybe be good though, to have Docker containers set up for situations when all is going south, like with this girl in my last workshop. In this case, we could provide instructions for instructors only, saying "ok, all is going wrong, before giving up, you could try to install Docker".
Apart from being a nice save, it could be a good way to make our instructors more comfortable with Docker and smooth a possible transition in the future. I would do it all in JupyterHub ; Sometimes, the best path is simply do one's best to make whatever path most pleasant for the end user. As a helper in the moment, I have had folks use wakari.
Which begs the question has anyone tried running this on a Chromebook with or without crouton? I've considered taking one of my Chromebooks to workshops as a backup. Not suggesting as a solution for this issue now. Just passing along as an excellent article to those that may be interested. In many cases, just providing a common namespace via environment-modules is often what is needed for reproducible setups across multiple platforms common in HPC : ref. Today at UW we had success following willingc 's suggestion to use git-osx-installer and skip the XCode download 1 , so I've mentioned that approach on the wiki too.
It was also mentioned earlier in this thread [2,3]. I think that's a solid enough solution to be sufficient for closing this issue. It's hard to link to wiki commits, but my full commit message is currently the most recent here 1. Okay, that's at odds with willingc 's comment above, but good to have a data point. It's definitely the stated goal of the git-osx-installer that it should work without XCode. One confounding factor to watch out for is that sometimes people may have installed the OS X command line tools without having installed Xcode.
That usually fixes all these problems, so something to watch out for. The instructions below outline installation of the current stable release v1. To install a different version of Compose, replace the given release number with the one that you want. Compose releases are also listed and available for direct download on the Compose repository release page on GitHub. To install a pre-release of Compose, refer to the install pre-release builds section. Docker Desktop for Mac and Docker Toolbox already include Compose along with other Docker apps, so Mac users do not need to install Compose separately.
Docker install instructions for these are here:. Docker Desktop for Windows and Docker Toolbox already include Compose along with other Docker apps, so most Windows users do not need to install Compose separately. If you are running the Docker daemon and client directly on Microsoft Windows Server, follow the instructions in the Windows Server tab.
Follow these instructions if you are running the Docker daemon and client directly on Microsoft Windows Server with Docker Engine - Enterprise , and want to install Docker Compose. Search for PowerShell, right-click, and choose Run as administrator. When asked if you want to allow this app to make changes to your device, click Yes. Because this directory is registered in the system PATH , you can run the docker-compose --version command on the subsequent step with no additional configuration.
Follow the instructions from the link, which involve running the curl command in your terminal to download the binaries. These step-by-step instructions are also included below. For alpine , the following dependency packages are needed: py-pip , python-dev , libffi-dev , openssl-dev , gcc , libc-dev , and make.
To install a different version of Compose, substitute 1. If you have problems installing with curl , see Alternative Install Options tab above.
Note : If the command docker-compose fails after installation, check your path. Optionally, install command completion for the bash and zsh shell. Compose can be installed from pypi using pip. If you install using pip , we recommend that you use a virtualenv because many operating systems have python system packages that conflict with docker-compose dependencies.