Task Network

[hismethod]

Please add option for task network.

[nicomt]

Hi @hismethod, I'm glad you're interested in the project. I'm looking into this issue, and I agree it would be good to have some control over the network config. But before I do something, it would be useful to understand your use case if possible.

Do you want this feature to be able to access the containers by domain name instead of IP? Is it to access a container in an existing network (created outside of ckron)? Is it for security isolation? Or is it something that I'm missing?

The docker-compose implementation seems like overkill for this project, so for now, I'm leaning towards a simpler implementation that might not address every problem

[hismethod]

First of all, I'm sorry for the late reply. To give you a quick answer, all three options that you mentioned are my requirements. First of all, I'm sorry for the late reply. To give you a quick answer, all three options you mentioned are requirements. One of the main reasons why a task item requires a Network item. It's security.

In my use case, the container must use another service in the docker network. There is a problem that the docker network is disconnected from the task container that the ckron operates, so the service port needs to be opened.

I think you already understand this situation.