Why does creating a custom network start Ryuk (ResourceReaper) immediately?

[JaySabva]

I’m seeing testcontainers/ryuk start as soon as I create a custom network, even when launching a single container. In CreateNetworkCmd setup, Testcontainers calls ResourceReaper.instance().getLabels() to
add cleanup labels:

labels.putAll(DockerClientFactory.DEFAULT_LABELS);
//noinspection deprecation
labels.putAll(ResourceReaper.instance().getLabels());
createNetworkCmd.withLabels(labels);

This call appears to initialize ResourceReaper, which starts Ryuk even when reuse is enabled. Is this expected? Is there a way to avoid starting Ryuk when creating a network (without globally disabling Ryuk or relying on reuse)?