Skip to content

Don't start temp container just to access volume#74

Merged
kevinmcconnell merged 1 commit into
mainfrom
dont-start-temp-container
Jun 24, 2026
Merged

Don't start temp container just to access volume#74
kevinmcconnell merged 1 commit into
mainfrom
dont-start-temp-container

Conversation

@kevinmcconnell

Copy link
Copy Markdown
Collaborator

When using a temporary container to get access to the mounted volume, there's no need to actually start a process there. The stopped container is enough.

When using a temporary container to get access to the mounted volume,
there's no need to actually start a process there. The stopped container
is enough.
Copilot AI review requested due to automatic review settings June 24, 2026 11:02

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR simplifies restore-time volume population by avoiding starting a “temp” container; it relies on a created (but not running) container purely as a mount point for copying data into the application volume.

Changes:

  • Remove the ContainerStart call for the restore temp container used in populateVolume.
  • Simplify the temp container config to only specify the image (no sleep infinity command).

Tip

If you aren't ready for review, convert to a draft PR.
Click "Convert to draft" or run gh pr ready --undo.
Click "Ready for review" or run gh pr ready to reengage.


💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@kevinmcconnell kevinmcconnell merged commit 28d47ce into main Jun 24, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants