Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow setting log_driver when using DockerSwarmOperator #40533

Open
1 of 2 tasks
xjchew opened this issue Jul 2, 2024 · 1 comment
Open
1 of 2 tasks

Allow setting log_driver when using DockerSwarmOperator #40533

xjchew opened this issue Jul 2, 2024 · 1 comment

Comments

@xjchew
Copy link

xjchew commented Jul 2, 2024

Description

Allow DockerSwarmOperator to be initialized with a log_driver argument which will be used by Docker SDK to create the service.

Use case/motivation

I have a Docker Swarm with all the nodes set to gelf logging driver as default. However, DockerSwarmOperator requires the services' logging driver to be json-file.
Allowing the logging driver to be specified when initializing the DockerSwarmOperator will allow services to be created with json-file logging driver in order for logs to be retrieved and shown in the UI.

Related issues

No response

Are you willing to submit a PR?

  • Yes I am willing to submit a PR!

Code of Conduct

@xjchew xjchew added kind:feature Feature Requests needs-triage label for new issues that we didn't triage yet labels Jul 2, 2024
Copy link

boring-cyborg bot commented Jul 2, 2024

Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval.

@dosubot dosubot bot added the area:core-operators Operators, Sensors and hooks within Core Airflow label Jul 2, 2024
@potiuk potiuk added good first issue provider:docker and removed area:core-operators Operators, Sensors and hooks within Core Airflow labels Jul 2, 2024
@RNHTTR RNHTTR removed the needs-triage label for new issues that we didn't triage yet label Jul 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants