devrelopers/fuchsia repository overview

⁠UNOFFICIAL

Use at your own risk.

⁠THIS IS BAD

Building massive toolkits like this in a Docker image is a bad idea, and should not be used by anyone, anywhere, ever, for any reason. Let it stand here as a warning to others: Don't do this! :D

⁠THIS IS HUGE

12GB. Seriously, look at the Dockerfile source and think about whether this image is useful to you. You probably want to invest the time in building Fuchsia for yourself.

⁠Source

This build process follows the steps outlined at fuchsia.dev here:

• https://fuchsia.dev/fuchsia-src/getting_started⁠
• ...and here: https://fuchsia.dev/fuchsia-src/development/source_code⁠

⁠Automation

Send a PR to the GitHub repo to make changes. If accepted, it will trigger a build here on the Docker Cloud. It takes about 45 minutes to an hour to complete on my laptop. It fails on the Docker Cloud service with the following error: Error processing tar file(exit status 1): write /fuchsia/prebuilt/third_party/fonts/noto-cjk/NotoSerifCJK-Bold.ttc: no space left on device because it is too big! Bummer.

⁠Instead of Automation

I'll build this on my laptop and upload on my gigabit fiber Internet connection as I have time. Ping me @davidcanhelp on Twitter or Keybase if you'd like to help, too!

⁠What this will become

At some point I'll stop using a sledge-hammer and come at this with a scalpel and make it a multistage build that spits out a much smaller image. Even then, you probably want to be building all this on your own. The Dockerfile over in GitHub may serve as a guide to see the steps laid out for you, but keep in mind that Fuchsia is in its early stages and the only, ONLY source of truth on this is Google and whatever they decide to do with their project. Keep your eye on https://fuchsia.dev/⁠ for their official instructions, and treat this Docker Cloud and GitHub experiment as exactly what it is: an experiment.