1. 06 Aug, 2018 1 commit
    • David Johnson's avatar
      In docker image emulabization, attempt to combine COPY instructions. · 18361092
      David Johnson authored
      We now try to emulate any simple COPY <src> <dst> instructions via rsync
      prior to image build.
      
      This *does* mean that artifact builder scripts must be careful to create
      all necessary dirs according to the base image semantics, because the
      base image content is not there when we emulate the COPY instructions.
      For instance, many of the modified Dockerfile-runit and
      runit-artifacts.sh files depended on built runit packages being
      installed into /tmp in the final image -- but they didn't create the
      /tmp dir because the COPY instruction they used was running atop a
      fully-populated base image that already had /tmp.  Thus, the
      runit-artifacts.sh scripts had to be changed to create /tmp with the
      proper permissions.
      18361092
  2. 10 May, 2018 1 commit
  3. 15 Nov, 2017 1 commit
    • Elijah Grubb's avatar
      Built out emulabizatization of docker alpine · 134e809f
      Elijah Grubb authored
      The organization of the code follows the guidelines set by the
      ubuntu version extremely closely. Big differences to notice are
      some of the package name changes switching from apt-get to apk,
      the requirement of the --disable-ssl flag when running the configure
      command for pubsub and the methodology required to build a custom
      apk package to use our custom runit. Apk has lots of issues and
      argues against building a new .apk package as root, so
      runit-artifacts.sh creates a new user, gives them super user permissions,
      adds them to the abuild group and runs the runit-packager.sh script
      as this new user. Design of this solution was focused on doing as
      much as possible while remaining in root. Enjoy!
      134e809f