G
YouTube TikTok Games
Skip to content

Persistent containers using container tunnel #77

Description

In the current implementation, a Container that needs to be persistent cannot depend on the container tunnel to reach endpoints on the host network. The reason is that the tunnel itself is not persistent.

The tunnel consists of 2 proxies actually:

  1. The container proxy that handles connection requests coming from other containers on the same container network
  2. The server proxy that proxies traffic from container proxy to desired host services (back-ends) that serve it.

The server proxy is a regular process (dcp tunnel-server). To enable tunnel persistence, we need support for persistent Executables, and then make the tunnel persistent (on demand) too.

Activity

  1. haliaeetusvocifer commented on Apr 17, 2026

    @haliaeetusvocifer
    Contributor

    I have started working on this

  2. haliaeetusvocifer commented on Apr 18, 2026

    @haliaeetusvocifer
    Contributor

    What is the status of #13 and can partial work (client-side only) be welcome?

  3. karolz-ms commented on Apr 18, 2026

    @karolz-ms
    CollaboratorAuthor

    Oluwasegun Haziz (@haliaeetusvocifer) this is an issue that is pretty much impossible to solve properly without #13. We are planning to address this as part of #9 work stream.

    I would suggest #106 as a good "next level" issue to work on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area-orchestratorAffects DCP usage in Microsoft AspireenhancementNew feature or request

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions