Docker networks

[LucasAguirre99]

What would you like to be added?

When performing the conversion in a docker compose that has a network, the command fails, causing automated processes to stop the pipeline or development

Why is this needed?

I guess it would be a good alternative that when performing the conversion, if our compose has a network it will be skipped, so our processes can continue since the network is not important in kubernetes

[stappersg]

It feels wrong to skip network.

Regarding the

since the network is not important in kubernetes

Thing is that it is important for the Docker compose file.

[LucasAguirre99]

Yes, what I mean is not that it is not present in the Dockerfile, I mean that if there is a defined network, kompose should skips it instead of failing, since it slows down many automations.

I don't know if I'm being clear

[stappersg]

On Mon, Nov 11, 2024 at 05:06:07AM -0800, Lucas Aguirre wrote: I don't know if I'm being clear

Let me try a new attempt. For the Docker compose file are network definitions important. Bailing out with an error on conversion has the benefit of drawing human attention. That is much better as "silent ignore", a.k.a. skipping. A websearch on "Chesters fence" might provide additional information. Groeten Geert Stappers P.S. Note to my further self: Let handle k8s-triage-bot handle this. -- Silence is hard to parse

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten