aboutsummaryrefslogtreecommitdiff
path: root/docker/base/start.sh
AgeCommit message (Collapse)AuthorFilesLines
2026-07-06Migrate to pyproject.tomlMichal Nasiadka1-27/+0
[tool.setuptools.data-files] does not support recursive directory installation. The old setup.cfg [files] worked because PBR's FilesConfig.expand_globs() used os.walk() to expand docker/*, but this hook is not triggered by the pbr.build PEP-517 backend. Move docker/ into kolla/ and use [tool.setuptools.package-data] instead. Update kolla_worker._get_images_dir() to check the kolla package directory first so both editable and regular installs work. Change-Id: I4fc452c03740ef22ebbb4e8d0d86c4f4783e2d09 Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
2024-09-26dev-mode: Run kolla_install_projects using sudoMichal Nasiadka1-1/+1
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
2024-09-04Refactor dev modeRoman Krček1-0/+3
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/<project_name> 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 <roman.krcek@tietoevry.com>
2020-10-05Be strict about errors in startRadosław Piliszek1-0/+3
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
2019-10-12Custom CA certificates installation mechanismViktor Michalek1-0/+3
Change-Id: I0fd596d93a0e575a391250d4bed261ad370a3664
2017-08-16Enable xtrace on start scriptsPaul Bourke1-0/+1
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
2017-05-29Remove all Heka related remaining stuffBertrand Lallau1-7/+0
Heka has been removed and replaced by fluentd. Refer to https://review.openstack.org/#/c/437874/ Change-Id: I989e5d71b5ba4d036dd45c02b3923c5bf27a04ed
2017-05-11Move shebang customization into jinja2 blockMartin André1-1/+1
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
2016-08-31Merge "Use dumb-init to manage the pid 1 process"Jenkins1-1/+1
2016-08-29Change source with dot at extend_start filesEduardo Gonzalez1-1/+1
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 <dabarren@gmail.com>
2016-08-20Use dumb-init to manage the pid 1 processJeffrey Zhang1-1/+1
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
2016-03-07Fix "wait for log socket" in start.shÉric Lemoine1-1/+1
The code in docker/base/start.sh that waits for the log socket does not work because it includes a bad "space" character after "-S". This patch changes that character to a real "space" character. It also sets the SKIP_LOG_SETUP envvar for the Heka container. TrivialFix Change-Id: I17a3005df5bbd57678350fc77030e44b5ad6acae
2016-02-23Merge "Remove Rsyslog entirely"Jenkins1-10/+0
2016-02-23Remove Rsyslog entirelyÉric Lemoine1-10/+0
Partially implements: blueprint heka Change-Id: I1322d2dc870e6f8fe052926995d993e8a08a25db
2016-02-23Skip extend_start.sh if KOLLA_SKIP_EXTEND_START is definedAngus Salkeld1-2/+4
This is all kolla-mesos needs, so that we can run the extend_start within the context of our start script. We need to do this to track dependencies of the commands (one of which is the extend_start). implements blueprint custom-extend-start Change-Id: Ib844adc9c42dd8862281eb3f903d6c2b4695a34d
2016-02-19Add Heka to common roleÉric Lemoine1-0/+7
Partially implements: blueprint heka Change-Id: I9ddad09b3f16b323c7ed535243458b0de6620cdb
2016-02-16Move socket binding to named_volumeSamYaple1-0/+10
The extend_start.sh script for rsyslog is removed as it is no longer needed. Docker no longer binds to /dev/log or /run/kolla/log Closes-Bug: #1544545 Change-Id: Ic0a323a26ee4e9e15baf4598285844a8a4955f23
2016-01-16Fix container config files directory pathWanlong Gao1-1/+1
TrivialFix Change-Id: I94dd94b1e64a6a844497e551a66e7279de636f90
2015-11-09Base image changes for drop-rootSteven Dake1-2/+4
The reason we are doing drop root is so that a network exposed software component (i.e. glance) cannot be used to affect the immutability of the container which it runs in. I have tried several different approaches and this is the only approach which puts glance in PID=1 while ensuring no files may be written by the glance process in the container image except for the log files. Change-Id: Ifd3c8c361b78d0e4791dade3afa6435290407c41 Partially-Implements: blueprint drop-root
2015-10-06Bring Kolla inline with FHSSam Yaple1-1/+1
This brings Kolla images inline with FHS and should make finding locations of things more consistent and reliable with the linux world at large. Change-Id: Iece5b4da4bace0fb8b1f41a65ab2c852ec73e6f8 Closes-Bug: #1485742
2015-10-06Common start.shSam Yaple1-0/+13
The majority of the start.sh code is identical. This removes that duplicate code while still maintaining the ability to call code in a specific container. The start.sh is moved into /usr/local/bin/kolla_start in the container The extend_start.sh script is called by the kolla_start script at the location /usr/local/bin/kolla_extend_start . It always exists because we create a noop kolla_extend_start in the base directory. We override it with extend_start.sh in a specific image should we need to. Of note, the neutron-agents container is exempt from this new structure due to it being a fat container. Additionally, we fix the inconsistent permissions throughout. 644 for repo files and the scripts are set to 755 via a Docker RUN command to ensure someones local perm change won't break upstream containers. Change-Id: I7da8d19965463ad30ee522a71183e3f092e0d6ad Closes-Bug: #1501295
generated by cgit v1.2.3 (git 2.39.1) at 2026-11-05 19:25:36 +0000