Page MenuHomeDevCentral

Sync novolume image
ClosedPublic

Authored by dereckson on Feb 12 2022, 22:40.
Tags
None
Referenced Files
F3716689: D2523.id6361.diff
Tue, Nov 5, 18:09
Unknown Object (File)
Sun, Nov 3, 02:03
Unknown Object (File)
Sat, Nov 2, 19:37
Unknown Object (File)
Thu, Oct 31, 09:02
Unknown Object (File)
Thu, Oct 31, 06:32
Unknown Object (File)
Wed, Oct 30, 08:16
Unknown Object (File)
Mon, Oct 28, 16:55
Unknown Object (File)
Mon, Oct 28, 00:23
Subscribers
None

Details

Summary

Offer OS upgrade to applications dependent images.

Ref T1679.

Image entry point

The runsvdir-init script, used for images based on Debian Jessie, controls
how this image run runit.

On Jessie, it saved environment, then call a script added by the Debian package
maintainer, runsvdir-start. That start script cleared environment and then
launch runit with /etc/service as services directory.

On Buster and Bullseye, runsvdir-start isn't available anymore. The first idea
was to ask images to directly call runit themselves. Yet, to ease maintenance,
it's clearly more efficient to have an unique entry point and be able to tweak
how we run the services. As such, we still provide runsvdir-init.

Test Plan

Rebuild PHP applications images

Diff Detail

Repository
rDPHPVIIFPM Docker image to install nginx, PHP 7 and fpm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

dereckson created this revision.

Restore /usr/local/sbin/runsvdir-init: applications container calls that file

Address runsvdir-init deprecation

Don't deprecate runsvdir-init, even if runsvdir-start isn't shipped by runit, we can maintain how we launch runit

This revision is now accepted and ready to land.Feb 13 2022, 16:35
This revision was automatically updated to reflect the committed changes.