A detached container cannot be accessed (at least with Kubernetes backend)

[stevapple]

Component

agent

Describe the bug

A detached container cannot be accessed by its name, making it unusable.

Steps to reproduce

1. Install Woodpecker and configure Kubernetes backend;
2. Run a detached step and access it in following steps with its name;
3. See "bad DNS name" or similar reports.

Expected behavior

As documented, a detached step should behave like a service. If it cannot be accessed by DNS, it is not capable of replacing service.

System Info

{
    "source": "https://github.com/woodpecker-ci/woodpecker",
    "version": "2.8.0"
}

Additional context

#3411 should be favorable...

Validations

• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Checked that the bug isn't fixed in the next version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]

[qwerty287]

Is there a reason to not use a service?

[stevapple]

@qwerty287 Our main service needs to start after all other services are ready, and we're now using a wait step for it.

If we want to use service, the only way is to allow a service to depend on a step, or support health check and dependency between services.