-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
False
-
-
False
-
-
[4002293530] Upstream Reporter: Shifa Khan
Upstream issue status: Open
Upstream description:
The `generate-containerfile.sh` script is designed to create new version directories (`cuda/13.2/`, `python/3.13/`, etc.) from templates. It intentionally exits with an error if the target directory already exists to prevent accidental `app.conf` overwrites.
This works well for adding new versions, but creates friction for template-only changes. When editing `Containerfile.cuda.template` or `Containerfile.python.template`, there's no automated way to propagate those changes to existing version directories.
*Current workaround:*
`cp Containerfile.cuda.template cuda//Containerfile` and `cp Containerfile.python.template python//Containerfile`
This works but isn't documented and requires knowing that `app.conf` files are version-specific while `Containerfile` is just a copy of the template.*References:*
- Related commit that introduced the current behavior: ca3c6a567b527bcaed29c657b8c17e2b7b8eff16
- links to