chore: proposed implementation plan#140
Conversation
| - stdin inspect JSON input | ||
|
|
||
| 2. **image enrichment** | ||
| - load image facts when available so image-defined defaults can be recognized and handled consistently |
There was a problem hiding this comment.
Inspecting the image and getting it's defaults. This will allow the library to distinguish “this was explicitly set on docker run” from “this came from the image.” In very specific cases it's also needed. Example from Codex:
there are cases where the absence of a value in container inspect is only meaningful relative to the image default.
Example:
docker run --entrypoint="" image-with-entrypoint sh
The container’s effective entrypoint is empty. If runlike only sees container inspect and emits:
docker run image-with-entrypoint sh
the clone will inherit the image’s default entrypoint, which is wrong. To know that empty entrypoint means “explicitly reset image entrypoint,” runlike needs image facts.
| Each dictionary entry covers one canonical option or one tightly related option group and records: | ||
|
|
||
| - canonical output form; | ||
| - equivalent spellings and aliases; |
There was a problem hiding this comment.
This might mean that the insect | runlike | run | inspect loop won't work simplistically since there can be equivalent but different options. At least the comparator should be aware of this and forgive insignificant differences (e.g. -i, --interactive).
|
closing this PR. all further work will continue on the fork https://github.com/shaninja/runlike |
2 participants
No description provided.