-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replace puppet 'docker' with containers #2935
Comments
We'll need to decide whether to write custom python scripts, or |
Another supporting fact regarding the divergence between two puppet environments, was the requirement of installing nodejs from a |
We'll look into replacing vagrant with rancher's integration with docker swarm. |
We need to look into implementing rancher compose, configuration files. |
We may need not need cygwin. However, all distro's will need |
In order for our current |
Trying to append to the Step 16/16 : RUN echo $(head -1 /etc/hosts | cut -f1) 'nginx-web' >> /etc/hosts && echo "hostname: $(hostname)"
---> Running in 8519bccb1d13
hostname: 8519bccb1d13 Additionally, running the Step 16/16 : RUN echo $(head -1 /etc/hosts | cut -f1) nginx-web >> /etc/hosts && echo "hostname: $(hostname)" && hostname nginx-web && echo "hostname2: $(hostname)"
---> Running in 8873d524abba
hostname: you must be root to change the host name |
So, we attempted to force docker to use the Step 16/17 : USER root
---> Running in 98460e35d31b
Removing intermediate container 98460e35d31b
---> 6356bba11f3e
Step 17/17 : RUN echo $(head -1 /etc/hosts | cut -f1) 'nginx-web' >> /etc/hosts && echo "hostname: $(hostname)" && hostname 'nginx-web' && echo "hostname2: $(hostname)"
---> Running in 212d6261fb7c
hostname: you must be root to change the host name Note: another option we have, in addition to those discussed above, is to possibly run the puppet provisioning during an |
Our |
#2935: Replace puppet 'docker' with containers
Our intention with our docker containers, was to use them for unit testing our application as a whole, while testing the validity of the puppet scripts, used to build our development environment. However, this basis is not really valid, since we implement the
docker
puppet environment, which is beginning to change from thevagrant
environment. This means, our docker containers are no longer checking the validity of puppet logic, used to build our development environment. And since the requirements of docker, and vagrant is not always a one-to-one relationship, we won't always be able to reuse the exact puppet script(s) between thevagrant
anddocker
puppet environments.Additionally, running puppet in docker, is similarly flawed to #2932. Therefore, we will eliminate our puppet implementation, within our docker containers, used for unit testing. This means we'll remove entirely the
docker
puppet environment, create an equal number of dockerfile's, as the number of puppet modules defined in ourvagrant
puppet environment, and adjust our.travis.yml
, respectively.The text was updated successfully, but these errors were encountered: