##// END OF EJS Templates
automation: schedule an EC2Launch run on next boot...
automation: schedule an EC2Launch run on next boot Without this, launching EC2 instances constructed from the AMI won't go through the normal EC2 instance launch machinery. This missing machinery does important things like set up network routes to use the instance metadata service and process any UserData. Since EC2Launch now runs on subsequent boots and UserData is processed, we needed to make setting of UserData conditional on bootstrapping mode. Differential Revision: https://phab.mercurial-scm.org/D7113

File last commit:

r38475:11eda1f1 default
r43509:20402153 default
Show More
fedora21
15 lines | 263 B | text/plain | TextLexer
Gregory Szorc
packaging: move most of contrib/docker to contrib/packaging/docker...
r38023 FROM fedora:21
Gregory Szorc
packaging: consistently create build user in Dockerfiles...
r38475
RUN groupadd -g 1000 build && \
useradd -u 1000 -g 1000 -s /bin/bash -d /build -m build
Gregory Szorc
packaging: move most of contrib/docker to contrib/packaging/docker...
r38023 RUN yum install -y \
gcc \
gettext \
make \
python-devel \
python-docutils \
rpm-build
# For creating repo meta data
RUN yum install -y createrepo