jnstockley opened a new issue, #53646:
URL: https://github.com/apache/airflow/issues/53646

   ### Apache Airflow version
   
   3.0.3
   
   ### If "Other Airflow 2 version" selected, which one?
   
   _No response_
   
   ### What happened?
   
   According to the docs here, 
https://airflow.apache.org/docs/apache-airflow/stable/cli-and-env-variables-ref.html#api-server,
 the api-server sub-command should have a name argument of `--log-config` but 
when the command field in the docker compose file is set to `api-server 
--log-config=<file_path>` the following error is shown `airflow command error: 
unrecognized arguments: --log-config=<file_path>, see help above.` I have also 
tried doing `api-server --log-config <file_path>` with a similar error message 
`airflow command error: unrecognized arguments: --log-config <file_path>, see 
help above.`
   
   
   
   ### What you think should happen instead?
   
   Preferably the api-server component should be updated to re-include this 
named argument, with the help message updated, or the docs should be updated to 
remove this name argument.
   
   ### How to reproduce
   
   In the provided docker-compose.yaml file, update the airflow-apiserver 
serivce command to be `api-server --log-config <file_path>`
   
   ### Operating System
   
   Debian
   
   ### Versions of Apache Airflow Providers
   
   _No response_
   
   ### Deployment
   
   Other Docker-based deployment
   
   ### Deployment details
   
   Custom docker image based on official docker image
   
   ### Anything else?
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to