[PR #56] [MERGED] Separate init script from the start script #191

Closed
opened 2026-03-01 18:33:43 +03:00 by kerem · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/netbootxyz/docker-netbootxyz/pull/56
Author: @dezeroku
Created: 1/31/2024
Status: Merged
Merged: 2/4/2024
Merged by: @antonym

Base: masterHead: to-upstream-two


📝 Commits (1)

  • cdae9b6 Separate init script from the start script

📊 Changes

2 files changed (+78 additions, -74 deletions)

View changed files

root/init.sh (+76 -0)
📝 root/start.sh (+2 -74)

📄 Description

In k8s environments it's quite common to bootstrap the deployments following these steps:

  1. Initialize the environment using upstream container
  2. Apply local customizations with a script
  3. Run the upstream container "as usual"

Currently there's no easy way to perform the initial configuration without starting the main processes, this PR separates "init" and "run" parts.

The init.sh file is basically copied as-is from the start.sh with two changes:

  1. removed the unnecessary backslash with a trailing space after then in line 30, as it was causing /start.sh: line 30: : not found warning/error
  2. wrapped echoed variable in double quotes in line 70

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/netbootxyz/docker-netbootxyz/pull/56 **Author:** [@dezeroku](https://github.com/dezeroku) **Created:** 1/31/2024 **Status:** ✅ Merged **Merged:** 2/4/2024 **Merged by:** [@antonym](https://github.com/antonym) **Base:** `master` ← **Head:** `to-upstream-two` --- ### 📝 Commits (1) - [`cdae9b6`](https://github.com/netbootxyz/docker-netbootxyz/commit/cdae9b68975826560cb2ccb9a4662aa2c66d01a2) Separate init script from the start script ### 📊 Changes **2 files changed** (+78 additions, -74 deletions) <details> <summary>View changed files</summary> ➕ `root/init.sh` (+76 -0) 📝 `root/start.sh` (+2 -74) </details> ### 📄 Description In k8s environments it's quite common to bootstrap the deployments following these steps: 1. Initialize the environment using upstream container 2. Apply local customizations with a script 3. Run the upstream container "as usual" Currently there's no easy way to perform the initial configuration without starting the main processes, this PR separates "init" and "run" parts. The `init.sh` file is basically copied as-is from the `start.sh` with two changes: 1. removed the unnecessary backslash with a trailing space after `then` in line 30, as it was causing `/start.sh: line 30: : not found` warning/error 2. wrapped echoed variable in double quotes in line 70 --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
kerem 2026-03-01 18:33:43 +03:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/docker-netbootxyz#191
No description provided.