Skip to content

feat: add runtime and init-image support (TDD)#3

Draft
explicitcontextualunderstanding wants to merge 76 commits intomainfrom
feature/runtime-init-image
Draft

feat: add runtime and init-image support (TDD)#3
explicitcontextualunderstanding wants to merge 76 commits intomainfrom
feature/runtime-init-image

Conversation

@explicitcontextualunderstanding
Copy link
Copy Markdown
Owner

Adds runtime and init_image mapping (maps to --runtime and --init-image) with docs and tests. Draft PR.

Mcrich23 and others added 28 commits January 28, 2026 16:49
* update to container 0.8

* test fixes

* network ip passthrough fixes

* warning fixes
Updated contribution guidelines to reflect new branch naming and testing requirements.
Added guidelines for contributing to the project.
* Sanitize project name when using directory name

We use the directory name as project name if none is specified. However directory names can contain a '.', which seems an invalid character for container names - at least I get errors when creating from `.devcontainers`.

This PR just replaces '.'  with '_', however there might be more forbidden characters we should replace?

* Added unit test for testDeriveProjectName
* Handle compose down with container_name case

* Providing tests for `container-compose down`

This provies the missing tests for PR Mcrich23#39

* Correctly asserting up/down

* Added copyYamlToTemporaryLocation as test helper

* Addressing code review

* test expect cleanup for containers running and stopping

* Update ComposeDownTests.swift

* Update ComposeDownTests.swift

* Update ComposeDownTests.swift

---------

Co-authored-by: rtoohil <ryan@ryantoohil.com>
Co-authored-by: Morris Richman <81453549+Mcrich23@users.noreply.github.com>
The entrypoint override was being appended after the image name,
causing it to be treated as container process arguments instead
of a `container run` flag. This meant the image's built-in
entrypoint was never overridden.

Fix: split entrypoint into --entrypoint <cmd> (before image)
and remaining args (after image), matching `container run` CLI
semantics.

Fixes containers immediately exiting when entrypoint is set in
docker-compose YAML.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- until now all waits always failed on 30 second timeout
- user is now informed that container is running
The RuntimeStatus type was introduced by TomasLudvik's commits but
doesn't exist in the container library. Removing the status tracking
since it was only used for error messages.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…to build run args for services and unit tests verifying restart, init, and entrypoint ordering.\n\nCo-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…untime and init_image fields to Service model, docs and tests.\n\nCo-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…tializer\n\nCo-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
… streamCommand valid\n\nCo-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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.

9 participants