public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "William Hubbs" <williamh@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-containers/docker/
Date: Sun, 23 Apr 2023 21:34:12 +0000 (UTC)	[thread overview]
Message-ID: <1682285635.38fde13b32c8ab8a523e7bda0d4bac64a97befe0.williamh@gentoo> (raw)

commit:     38fde13b32c8ab8a523e7bda0d4bac64a97befe0
Author:     William Hubbs <williamh <AT> gentoo <DOT> org>
AuthorDate: Sun Apr 23 21:33:55 2023 +0000
Commit:     William Hubbs <williamh <AT> gentoo <DOT> org>
CommitDate: Sun Apr 23 21:33:55 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=38fde13b

app-containers/docker: warn and link docs for CONFIG_RT_GROUP_SCHED

Bug: https://bugs.gentoo.org/904264
Signed-off-by: William Hubbs <williamh <AT> gentoo.org>

 app-containers/docker/docker-23.0.3.ebuild | 1 +
 1 file changed, 1 insertion(+)

diff --git a/app-containers/docker/docker-23.0.3.ebuild b/app-containers/docker/docker-23.0.3.ebuild
index c03ce70575dd..a2754cb1e601 100644
--- a/app-containers/docker/docker-23.0.3.ebuild
+++ b/app-containers/docker/docker-23.0.3.ebuild
@@ -167,6 +167,7 @@ pkg_setup() {
 		~IP_VS_PROTO_UDP
 		~IP_VS_RR
 		"
+	WARNING_RT_GROUP_SCHED="CONFIG_RT_GROUP_SCHED is disabled: Depending on your docker setup, you may want to enable this. See https://docs.docker.com/config/containers/resource_constraints/#configure-the-realtime-scheduler for more information."
 
 	if use selinux; then
 		CONFIG_CHECK+="


             reply	other threads:[~2023-04-23 21:34 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-23 21:34 William Hubbs [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-04-11 14:35 [gentoo-commits] repo/gentoo:master commit in: app-containers/docker/ William Hubbs
2025-03-16 22:05 William Hubbs
2025-03-16 10:19 Sam James
2025-03-16  6:27 Arthur Zamarin
2025-03-16  6:27 Arthur Zamarin
2025-03-05 17:50 William Hubbs
2025-02-26 21:43 William Hubbs
2025-01-28 14:52 William Hubbs
2025-01-15 14:08 William Hubbs
2025-01-14  7:25 Arthur Zamarin
2025-01-14  2:32 Sam James
2025-01-14  2:20 Sam James
2024-12-25 20:14 William Hubbs
2024-12-20  4:17 William Hubbs
2024-12-09 23:36 William Hubbs
2024-10-30 14:02 William Hubbs
2024-09-05  0:18 William Hubbs
2024-09-05  0:14 William Hubbs
2024-08-27 19:20 William Hubbs
2024-08-27 19:09 William Hubbs
2024-07-02  3:13 William Hubbs
2024-06-13 17:57 Sam James
2024-06-13  2:15 Sam James
2024-06-13  1:56 Sam James
2024-04-26  5:08 William Hubbs
2024-03-17 14:56 William Hubbs
2024-02-15 15:47 William Hubbs
2024-02-01 16:24 William Hubbs
2023-11-09 22:54 William Hubbs
2023-09-25 19:20 William Hubbs
2023-07-24 21:08 Sam James
2023-07-24 21:04 Sam James
2023-07-24 20:54 Sam James
2023-07-24 19:54 William Hubbs
2023-07-24 19:40 William Hubbs
2023-07-21 23:52 Sam James
2023-07-21 21:52 Sam James
2023-07-21 15:16 William Hubbs
2023-07-21 15:14 William Hubbs
2023-07-20 19:33 William Hubbs
2023-05-27 15:29 Sam James
2023-04-23 21:34 William Hubbs
2023-04-13  0:55 Sam James
2023-04-13  0:55 Sam James
2023-04-13  0:55 Sam James
2023-04-07 17:48 William Hubbs
2023-03-15 17:40 William Hubbs
2023-03-14 16:50 William Hubbs
2023-03-11 22:54 Sam James
2023-03-11 19:23 Sam James
2023-03-11 18:50 Sam James
2023-03-11 18:50 Sam James
2023-03-10 22:18 William Hubbs
2023-03-10 21:35 William Hubbs
2023-01-07 19:33 William Hubbs
2023-01-05  5:39 William Hubbs
2023-01-05  5:05 Sam James
2023-01-03 19:34 William Hubbs
2023-01-03 19:16 Arthur Zamarin
2023-01-03 16:04 William Hubbs
2022-08-20 22:09 William Hubbs
2022-08-19 19:33 Arthur Zamarin
2022-08-15  7:42 Agostino Sarubbo
2022-08-15  7:40 Agostino Sarubbo
2022-05-17 14:52 William Hubbs
2022-04-15  2:12 William Hubbs
2022-04-04 21:33 William Hubbs
2022-04-04 15:28 William Hubbs
2022-04-01  4:30 Sam James
2022-02-14  9:48 Jakov Smolić
2022-01-07 18:06 Georgy Yakovlev
2022-01-07 17:55 Georgy Yakovlev

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1682285635.38fde13b32c8ab8a523e7bda0d4bac64a97befe0.williamh@gentoo \
    --to=williamh@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox