Live data from Hacker News

ResinOS, run Docker containers on embedded devices

resinos.io

1–10 of 73 posts

Re: ResinOS, run Docker containers on embedded devices

#4

Very cool stuff! Some boards, like the beaglebone, have specialized hw like PRUs or I2C pins. Is it possible to access these with Docker containers? Also, what is the minimum memory footprint? i.e. how many containers can I fit within say 1 GB.

The version of Docker on the OS right now is 1.10 so the ram footprint of the OS is fairly small. The team is all asleep (being in Berlin and whatnot), but I'd estimate about 50mb is a decent approximation. We're working on getting a newer Docker but its RAM footprint is one of our concerns, though we do have ways forward.

The number of containers is kinda a red herring for a couple reasons. For one, you can make a trivial container and launch as many containers as you like, it really depends on what's in them. For another, embedded devices don't usually need hundreds of containers, they run payloads that are either single-container, or look a lot more like a docker-compose file with a few microservices.

Re: ResinOS, run Docker containers on embedded devices

#5

Very cool stuff! Some boards, like the beaglebone, have specialized hw like PRUs or I2C pins. Is it possible to access these with Docker containers? Also, what is the minimum memory footprint? i.e. how many containers can I fit within say 1 GB.

The version of Docker on the OS right now is 1.10 so the ram footprint of the OS is fairly small. The team is all asleep (being in Berlin and whatnot), but I'd estimate about 50mb is a decent approximation. We're working on getting a newer Docker but its RAM footprint is one of our concerns, though we do have ways forward. The number of containers is kinda a red herring for a couple reasons. For one, you can make a t…

quick question...would the images have to be specifically built for arm? (we were looking to build a cluster of RPis that we could orchestrate containers on.)

Re: ResinOS, run Docker containers on embedded devices

#6
Congrats on launching! Testing & deployment of stable configs is arguably even more of an issue in embedded development than in web, so I'm sure this will make a lot of people very giddy! Are y'all 100% happy with the technical design assumptions & requirements of Docker, or did you mainly pick it so you could bridge with the existing community (or a bit of both?)

Re: ResinOS, run Docker containers on embedded devices

#7
I always have trouble calling platforms that can run a system of this magnitude "embedded." For some reason I always had the term "single-purpose" linked with the idea of an embedded system. Once you add tons of RAM, a relatively powerful processor, and can only last a couple of hours on a battery--I feel like then it's just a small general purpose computer.

Re: ResinOS, run Docker containers on embedded devices

#8

Hi everyone, resin.io founder here, happy to answer any and all questions. We just released resinOS at ELCE a few hours ago (Embedded Linux Coference, Europe), happy to see it made HN!

How is this different from HypriotOS?

http://blog.hypriot.com

Re: ResinOS, run Docker containers on embedded devices

#9

Earlier quoted context omitted.

The version of Docker on the OS right now is 1.10 so the ram footprint of the OS is fairly small. The team is all asleep (being in Berlin and whatnot), but I'd estimate about 50mb is a decent approximation. We're working on getting a newer Docker but its RAM footprint is one of our concerns, though we do have ways forward. The number of containers is kinda a red herring for a couple reasons. For one, you can make a t…

quick question...would the images have to be specifically built for arm? (we were looking to build a cluster of RPis that we could orchestrate containers on.)

Yes - they would have to be built with ARM base images.

Re: ResinOS, run Docker containers on embedded devices

#10
post #7

I always have trouble calling platforms that can run a system of this magnitude "embedded." For some reason I always had the term "single-purpose" linked with the idea of an embedded system. Once you add tons of RAM, a relatively powerful processor, and can only last a couple of hours on a battery--I feel like then it's just a small general purpose computer.

I agree, but the definition of "embedded" has changed, with things like the Pi Zero being a full computer the size of a stick of gum.
Post reply on HN