Configure custom entry points and lifecycle hook scripts for Stage-1 and Stage-2 sequential image builds.

ℹ️ Important: Script Path Access Rules

🏗️ Stage-1 Scripts:

• Can ONLY reference paths starting with stage-1/
• Cannot access any stage-2/ paths (stage-2 doesn't exist yet)
• Examples: stage-1/custom/script.sh, stage-1/system/setup.sh

🚀 Stage-2 Scripts:

• Can reference paths starting with both stage-1/ and stage-2/
• Has access to all stage-1 resources plus stage-2 resources
• Examples: stage-2/custom/app.sh, stage-1/system/base.sh

Why? Stage-1 builds first and becomes the foundation. Stage-2 builds on top of Stage-1, inheriting all its resources.

🏗️ Stage-1 Image Scripts

Custom Entry Point

Override the default entry point for Stage-1

Use default File path Inline script

Lifecycle Scripts

Scripts that run at specific lifecycle events

on_build - Runs during Stage-1 image building

on_first_run - Runs on first container start (respective stage)

on_every_run - Runs on every container start (respective stage)

on_user_login - Runs when user logs in via SSH (respective stage)

🚀 Stage-2 Image Scripts