jamesob

> On a quick glance over the second commit, I saw that the help examples are not working, see comment below. Will review more in-depth within the next days. @theStack...

I think I've addressed all of @luke-jr, @Sjors' feedback - let me know if I've missed something.

I applied the following patch, which fixes the original error: ```diff diff --git a/Dockerfile b/Dockerfile index 7d42262..84ecb39 100644 --- a/Dockerfile +++ b/Dockerfile @@ -74,7 +74,7 @@ RUN npm ci #...

Solved the last problem by doing a recursive submodule clone: ```sh git submodule update --init --recursive ``` But I'm still failing on the entrypoint: ``` STEP 25/29: RUN /app/bin/docker_entrypoint.sh archivebox...

Okay, looks like the `archivebox` user didn't have read permissions on `/app`, which I think is explained by my host's umask (`umask 077`). So the complete patch set I needed...

FWIW I was seeing same behavior as OP and it was fixed (as suggested previously) by adding ```es6 uid={(i) => i.label} ``` to the component invocation.

Docker image ([`jamesob/bitcoind:bip324-enable`](https://hub.docker.com/layers/jamesob/bitcoind/bip324-enable/images/sha256-89cbe61ab22aa55424624ca2ceaa1f019e8757f8f55fdfef56a77eb4261a3069?context=explore)) built for this branch as of 062e51c2f051dc68197bc21535fd06b3e01bdc21, in case that helps anyone test.

Good for merge?

Also, is it worth adding a warning in `podman-compose` when we create a network that has `dns_enabled` = false and the compose file is also using `links:`? That might be...

Concept ACK, will try to review today or tomorrow.