harbor/make/photon/chartserver/docker-entrypoint.sh

#!/bin/bash
set -e


/home/chart/install_cert.sh

#Start the server process
exec /home/chart/chartm
Update the related build scripts to package the chart repo server add env file template for chart repo server in make/common/config/chartserver update the Makefiles to support build chart repo server add docker file and related build scripts for upstream chart server - chartmuseum update prepare to support generating chart server related configs add docker compose file for the chart server add build/install command options to install with/without chart repo server update install.sh to support chart repo server installation 2018-07-19 10:47:05 +02:00			`#!/bin/bash`
			`set -e`
Keep the chart server related configurations in adminserver append chart server related config options to the supporting list of adminserver provide chart server related config access method in the API layer update prepare script and ui env template file to enable cache driver config for chart server API append flag info in the systeminfo API to indicate if chart server is deployed with Harbor refactor the response rewriting logic to return structual error object add api init method to initilizing objects required in API handlers chage owner of the storage folder update offline/online package scripts in Harbor-Util.robot 2018-07-19 17:50:25 +02:00

Change chartmuseum container to non-root Signed-off-by: DQ <dengq@vmware.com> 2019-10-14 09:33:33 +02:00			`/home/chart/install_cert.sh`
Fix issues related with chart storage - inject custom CA bundle into chart repo - update prepare script to inject credentials Signed-off-by: Steven Zou <szou@vmware.com> 2018-08-27 10:18:07 +02:00
			`#Start the server process`
Use exec in all components' entrypoints Use the exec Bash command so that the final running application becomes the container’s PID 1. This allows the application to receive any Unix signals sent to the container, in accordance with https://docs.docker.com/develop/develop-images/dockerfile_best-practices/#entrypoint Currently, SIGTERM signals sent by kubernetes are not passed to the executed binary. Signed-off-by: Xavier Duthil <xavier.duthil@corp.ovh.com> 2021-03-05 15:00:22 +01:00			`exec /home/chart/chartm`