zlonghofer opened a new pull request, #47551:
URL: https://github.com/apache/airflow/pull/47551
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
-->
`containerd` fixes this upstream in [PR
8924](https://github.com/containerd/containerd/pull/8924) by removing the
`LimitNOFILE` declaration, relying on the underlying operating systems to set
minimum and maximum memory constraints. (This was pushed to `containerd` in
October 2023.)
`containerd` [release
notes](https://github.com/containerd/containerd/releases/tag/v2.0.0#:~:text=%238924)
for v2.0.0 reference the change.
The Docker Engine pulled this update from `containerd` in v25.0.0
([changelog](https://docs.docker.com/engine/release-notes/25.0/#:~:text=The%20daemon%20now,topic%20in%20detail.)).
I'm not sure there's a reason to keep these warnings in the documentation --
if I'm wrong, the documentation should at least be updated to indicate the
version of `containerd` and `docker` in which the issue is resolved.
--
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]
