openstack/kolla.git/docker/base/start.sh, branch stable/2026.1

dev-mode: Run kolla_install_projects using sudo

2024-09-26T11:40:32+00:00

Since packages are installed using root during image build - we need to use sudo when updating those packages when using dev-mode. Change-Id: Idf14e334d50abeb1719563b1733af0b8425b3b55

Refactor dev mode

2024-09-04T06:37:09+00:00

Provides mechanism for future work to fix bug where when package file manifest changes, the changes were not reflected in to devmode-enabled container. It changes the strategy of installing projects in dev mode in containers. Instead of bind mounting the project's git repository to the venv of the container, the repository is bind mounted to /dev-mode/ from which the it is installed using pip on every startup of the container using kolla_install_projects script. Related-bug: #1814515 Change-Id: Ia1bdff87cba73587a03124ab78a56b21c6176373 Signed-off-by: Roman Krček

Be strict about errors in start

2020-10-05T11:03:39+00:00

Make start.sh run with pipefail and nounset to avoid common errors in the start scripts and detect them early. Httpd code had to be patched to allow it to pass on Debuntu. Also fix the two missed applications of httpd to make sure all its path are covered. And also fix Horizon's ENABLE_ZAQAR - K-A does not use Zaqar. Yet another - Horizon's settings_bundle. :-) Finally, fix Neutron for Debuntu (KOLLA_LEGACY_IPTABLES). Change-Id: I39b8d78f6758df1f92b8b0d2c06ea99b038b843b Depends-On: https://review.opendev.org/711923

Custom CA certificates installation mechanism

2019-10-12T15:36:27+00:00

Change-Id: I0fd596d93a0e575a391250d4bed261ad370a3664

Enable xtrace on start scripts

2017-08-16T16:13:28+00:00

This helps operators more accurately see the start up sequence of containers, especially in the case where they fail and we want to see the last command executed. Change-Id: I8a5765f09d52bb11d5af5aa8886746c87757ea5f

Remove all Heka related remaining stuff

2017-05-29T01:42:20+00:00

Heka has been removed and replaced by fluentd. Refer to https://review.openstack.org/#/c/437874/ Change-Id: I989e5d71b5ba4d036dd45c02b3923c5bf27a04ed

Move shebang customization into jinja2 block

2017-05-11T15:54:17+00:00

By setting up the shebang inside a jinja2 block, this allows the operator to use a different init system of simply disable it. This is especially useful with docker 1.13 that comes with its own stripped down init system (a build of tini) that would cause the containers to run double init systems if used with the '--init' command line argument. Change-Id: I220d8cfc81c25471e635b2f5790759f21e788e64 Closes-Bug: #1680770

Merge "Use dumb-init to manage the pid 1 process"

2016-08-31T16:30:13+00:00

Change source with dot at extend_start files

2016-08-29T05:29:16+00:00

Is a best practice in Unix/Linux scripts to use dots instead of source command. Using dots will avoid issues with non BASH shells TrivialFix Change-Id: Ie6480a1954f853f79faffa093452715ebd9f7d90 Signed-off-by: Eduardo Gonzalez

Use dumb-init to manage the pid 1 process

2016-08-20T17:27:17+00:00

Normally, when you launch a Docker container, the process you're executing becomes PID 1, giving it the quirks and responsibilities that come with being the init system for the container. There are two common issues this presents: * In most cases, signals won't be handled properly. * Orphaned zombie processes aren't properly reaped. the dumb-init acting like a simple init system. It launches a single process and then proxies all received signals to a session rooted at that child process. Closes-Bug: #1614509 Change-Id: I9d3d04648e151ddc7c6732b92ffd3b6c9fe467ec