no package should be installed inside a container
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Michele Baldessari |
Bug Description
While deploying on a rhel8 os beta + pure f28 containers we noticed that during docker-puppet or during docker-
It makes zero sense to install packages inside a container because if you don't commit the container the content will be lost at restart anyway and so the installed package will be missing anyway.
root 60586 0.0 0.0 13948 2936 ? Ss 15:29 0:00 \_ /bin/bash /var/lib/
root 60623 6.8 0.7 366532 118236 ? Sl 15:29 0:04 \_ /usr/bin/ruby-mri /usr/bin/puppet apply --summarize --detailed-
root 60879 24.1 0.8 613968 137800 ? Ss 15:29 0:11 \_ /usr/bin/python3 /usr/bin/dnf -d 0 -e 1 -y install MySQL-python
The packages *must* be preinstalled in the container images all the time, assuming we can invoke yum/dnf inside the container makes little sense.
The reason for this is that this hiera key is set inequivocally: hiera.yaml tripleo: :packages: :enable_ install
[root@win1 hieradata]# hiera -c /etc/puppet/
true
This is set in /usr/share/ openstack- tripleo- heat-templates/ environments/ standalone/ standalone- tripleo. yaml