[Enhancement]: Instead of fixed to docker, I wish a independent container hosting implementation like kubernetes

Open
#1,512 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
csharp, docker, kubernetes
Domain
infrastructure, testing

Research direction

No files or tests are named. Start by mapping how the current Docker runtime is integrated and how Docker API connections are configured, then evaluate the proposed runtime abstraction and Kubernetes client scope. Done would require an agreed design and an implementation that supports container hosting on a remote Kubernetes cluster without depending on local Docker.

Written by the indexing model from the issue text.

Description

enhancement
Problem

Currently I have to use docker or test containers cloud to run test containers.

Because of company policy I'm not allowed to used any local subsystem like wsl or docker desktop.

I have some remote docker server, but by company policy I have to use docker.api over ssh which the nuget docker lib not supporting. (btw. I have a fork which enables this. I saw you have a fork, too. maybe you like my docker over ssh support)

I'm currently not able to us test containers, with the current implementation.

Solution

Put the container runtime into a strategy pattern and getting independent of docker runtime.
find abstractions to be later implemented in different container hostings.

finally implement a k8s client to run test container on remote k8s clusters.

Benefit

flexibility in hosting

Alternatives

don't now, that why i'm asking.

support docker over ssh in the dotnet ssh lib. (with key authentication)

Would you like to help contributing this enhancement?

No

Dominant language
C#
Stars
4.4k
Forks
357
Avg merge
14h 42m
Merged PRs (30d)
16

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from testcontainers/testcontainers-dotnet

All issues in testcontainers/testcontainers-dotnet

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.