d2dyno/eac3to-cli-docker repository overview

⁠Installation

Here are some example snippets to help you get started creating a container.

⁠docker

docker run \
  --name=eac3to-cli \
  -e PUID=99 \
  -e PGID=100 \
  -e TZ=America/Chicago \
  -v </path/to/raws>:/raws \
  d2dyno/eac3to-cli-docker "1)" /raws/SOMERAW

⁠CLI usage

1. ⁠Pull/update the image

docker pull d2dyno/eac3to-cli-docker

• ⁠Run single eac3to command without entering container shell

Be sure to edit as needed (Edit -v, "1)" and /raws/SOMERAW)

docker run --rm -v /path/to/raws:/raws d2dyno/eac3to-cli-docker z:/raws/SOMERAW "1)" -demux -progressnumbers

• ⁠Enter container shell, but don't run container after exiting.

docker run -it --rm -v /path/to/raws:/raws d2dyno/eac3to-cli-docker /bin/bash

• ⁠Run the container indefinitely (to later attach to)

docker run --detached=true --name=eac3to-cli-docker -v /path/to/raws:/raws d2dyno/eac3to-cli-docker tail -f /dev/null

⁠Later attach with

docker exec -it eac3to-cli-docker /bin/bash

⁠If you attached to the container shell, you can now run eac3to commands using eac3to

eac3to z:/raws/SOMERAW

eac3to z:/raws/SOMERAW "1)" -demux -progressnumbers

⁠Parameters

Container images are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate <external>:<internal> respectively.

⁠User / Group Identifiers

When using volumes (-v flags) permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the user PUID and group PGID.

Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.

In this instance PUID=99 and PGID=100, to find yours use id user as below:

  $ id username
    uid=1000(dockeruser) gid=1000(dockergroup) groups=1000(dockergroup)

⁠Support Info

• Shell access whilst the container is running: docker exec -it eac3to-cli /bin/bash
• To monitor the logs of the container in realtime: docker logs -f eac3to-cli
• container version number
  • docker inspect -f '{{ index .Config.Labels "build_version" }}' eac3to-cli
• image version number
  • docker inspect -f '{{ index .Config.Labels "build_version" }}' d2dyno/eac3to-cli-docker

⁠Updating Info

Below are the instructions for updating containers:

⁠Via Docker Run/Create

• Update the image: docker pull d2dyno/eac3to-cli-docker
• Stop the running container: docker stop eac3to-cli
• Delete the container: docker rm eac3to-cli
• Recreate a new container with the same docker create parameters as instructed above (if mapped correctly to a host folder, your /config folder and settings will be preserved)
• Start the new container: docker start eac3to-cli
• You can also remove the old dangling images: docker image prune

⁠Via Docker Compose

• Update all images: docker-compose pull
  • or update a single image: docker-compose pull eac3to-cli
• Let compose update all containers as necessary: docker-compose up -d
  • or update a single container: docker-compose up -d eac3to-cli
• You can also remove the old dangling images: docker image prune

⁠Via Watchtower auto-updater (especially useful if you don't remember the original parameters)

• Pull the latest image at its tag and replace it with the same env variables in one run:

  docker run --rm \
  -v /var/run/docker.sock:/var/run/docker.sock \
  containrrr/watchtower \
  --run-once d2dyno/eac3to-cli-docker
  

  Copy
• You can also remove the old dangling images: docker image prune