##// END OF EJS Templates
upstream » mercurial-mirror
RSS

Clone from https://www.mercurial-scm.org/repo/hg-all

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
Augie Fackler - - Load All Authors

File last commit:

r40621:d0a6b2c8 default
r43509:20402153 default
Show More
fedora29
15 lines | 263 B | text/plain | TextLexer
/ contrib / packaging / docker / fedora29
History | Annotation | Raw |Copy content |Copy permalink
FROM fedora:29
RUN groupadd -g 1000 build && \
useradd -u 1000 -g 1000 -s /bin/bash -d /build -m build
RUN dnf install -y \
gcc \
gettext \
make \
python-devel \
python-docutils \
rpm-build
# For creating repo meta data
RUN dnf install -y createrepo