-
Notifications
You must be signed in to change notification settings - Fork 8
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
doesnt work on docker for Mac #21
Comments
Yepp! Same for me here. Tried it on Ubuntu but there it just says:
|
@shaunmulligan @KemperVreden with which Resin OS versions does that happen? |
@jhermsmeier I tried with resinOS 1.24.1 on rpi3 from production. It doesn't seem to work on macOS because the thin hypervisor kernel they have in docker for Mac doesnt have the correct settings for btrfs. but Ubuntu 16.10 worked correctly for me after this PR: #20 |
@jhermsmeier 1.24.0 - Tested yesterday. On Raspberry Pi running stock-Raspbian it ran but got an error which said something about the "GO"-language when compiling something ... I can reproduce the output but since I am more interested running this script on OS X (macOS - I know) I am looking for a fix to get it working on my Mac BTW: Ubuntu didn't work. It just stopped. Do I have to modify the
|
Apparently they removed BTRFS support from Docker for Mac: docker/for-mac#388 @KemperVreden Which docker version are you running on Ubuntu? |
@jhermsmeier I am using 16.04 LTS |
@KemperVreden Sadly it doesn't look like BTRFS support will get back into Docker for Mac very soon, but I just merged the new version with enhanced log output and some other things – could you try that on Ubuntu and post the output, if it fails? That would be very helpful. Keep in mind you'll have to run |
Ok so running Running the script returns: |
This looks like there's something wrong with the network there:
I checked and it seems to be up & available:
Does restarting docker completely & retrying help?
Yeah, that's to be expected if the build step fails. |
@jhermsmeier Sure! I hade some bad network settings in my Ubuntu-VM. Fixed it and I successfully tried it again today. I cannot test the image but seems like everything just worked as expected!? https://gist.github.com/KemperVreden/529ca26488b16e03e060a9da91b7bdd8 |
@KemperVreden Nice, I'm glad it eventually worked! The output looks good, so if you used the current up-to-date master (there was a fix that went into it yesterday), the image should be fine as well. |
I'm closing this, as it appears resolved, and the documentation states the known issues around having to use the old Docker Toobox for btrfs support. |
Get the following error:
The text was updated successfully, but these errors were encountered: