Tomek's Mesos on ARM seems out of date, and it is a bit painful to set upa Raspberry Pi development environment in x86 machine.

So I create a docker image `haosdent/raspberry` to simple this and documenthow to patch, compile and running mesos on the Raspberry Pi in this [post](http://blog.haosdent.me/2016/04/24/mesos-on-arm/). Hope it is helpful foryou if you are seeking to run Mesos on ARM.

In additional, thanks to @zhiwei and @vinodkone's work recently. Bundlezookeeper package have already upgraded to 3.4.8 which could pass compileon ARM. The only change to make mesos pass compile on ARM is to patch `pivot_root` in fs.cpp. @Tomek would you like to modify it according to mysuggestions on your github and post it in review boardhttps://reviews.apache.org/groups/mesos/ to further review? I think it isnecessary if we want to make Mesos run on ARM perfectly.

We are working on a hack to run Mesos agents on Raspberry Pi and are wondering if anyone here has done that before. From the Google search results we looked at so far, it seems like it has been compiled, but we haven't seen an indication that anyone has run it and launched tasks on them. And does it sound right that it might take 4 hours or so to compile?

We are looking to run just the agents. The master will be on a regular Ubuntu laptop or a server.

Mesos builds were mostly already covered by notes from the community. There were a few other items that included challenges of running on corporate network in a company that runs everything on the ec2 cloud, time to burn 32G sd cards, etc. Will have more details later. Thanks.

As @haosdent mentioned with Kevin we tried to run it on ARM. AFAIR therewas a problem only with master, agents runs smoothly (or pretend to). Torun it on RPi you need to compile it for ARM. Easy but long solution is tocompile it on rpi. Quick but a little bit harder cross compile it on"normal" machine and upload to device.

I played around with Mesos on RPi a while back and have been able to compile and run it with 2 little patches.

1) Depending on the ZK version, it may be necessary to patch a function that uses inline ASM to use the resp. compiler intrinsics (I don’t remember where exactly in zk it was, but the compile error should tell you)

2) There is string formatting code somewhere that compiles, but is not architecture independent, i.e. behaves different on 32 and 64 bit. IIRC the fix was to change %lu to %llu or something close to that. The stack trace when Mesos crashes should tell you. If you’re lucky enough to have an RPi3, this may not be necessary.

Also, if you compile on the RPi make sure to create a swap file of >=512MB. The build process will use lots of memory. I have not been able to compile on multiple cores, because the memory usage was just too high.

We are working on a hack to run Mesos agents on Raspberry Pi and arewondering if anyone here has done that before. From the Google searchresults we looked at so far, it seems like it has been compiled, but wehaven't seen an indication that anyone has run it and launched tasks onthem. And does it sound right that it might take 4 hours or so to compile?

We are looking to run just the agents. The master will be on a regularUbuntu laptop or a server.

Apache Lucene, Apache Solr and all other Apache Software Foundation project and their respective logos are trademarks of the Apache Software Foundation.
Elasticsearch, Kibana, Logstash, and Beats are trademarks of Elasticsearch BV, registered in the U.S. and in other countries. This site and Sematext Group is in no way affiliated with Elasticsearch BV.
Service operated by Sematext