summaryrefslogtreecommitdiff
path: root/chef-system-x86_32-container.morph
Commit message (Collapse)AuthorAgeFilesLines
* Include foundation in chef-systemSam Thursfield2014-08-011-0/+3
| | | | | This increases the size to around 250MB, but it's required for libffi to work, and much other stuff no doubt.
* ADD NAME FIELD BECAUSE THE STRATUM IS IGNORED OTHERWISESam Thursfield2014-08-011-1/+2
|
* Chef imported into Baserock, prototype #2Sam Thursfield2014-07-311-1/+1
| | | | | | | | | Taking advantage of the new work in Morph 'master' allowing chunk morphs to go in definitions, we can now treat each Gem as a chunk, and with a bit of hackery, make fetching and compiling+installing the Gem from http://rubygems.org/ look like a normal Morph build. To avoid the hackery we need to introduce a separate build-mode, probably, but this is a start!
* REmove GCC binaries in the chef system manuallySam Thursfield2014-07-311-0/+1
| | | | | Nasty hack, but saves 200MB or about 50% of the total size of the system.
* Strip out ruby documentation from the chef systemSam Thursfield2014-07-311-0/+4
| | | | It's about 70MB, and not needed in a container.
* Don't include core-runtime, try pulling in just the OpenSSL libsSam Thursfield2014-07-311-1/+1
| | | | | The chef system is about 667MB with core-runtime included which seems excessive for a container!
* chef-system: OpenSSL libraries are needed at runtime.Sam Thursfield2014-07-311-0/+3
|
* Add Chef hack attempt #1Sam Thursfield2014-07-311-1/+1
| | | | | This uses a local repo with all the required Gems committed in advance and a script that runs 'gem install' as the build tool.
* Initial chef systemSam Thursfield2014-07-311-0/+16
Installs chef by running 'gem' at deploy time. Sorry.