Provides docker-compose alternative workflow for Valkyrie development

[dchandekstark]

This is to provide a docker-compose workflow for Valkyrie development.

[dchandekstark]

I need a consult on the Dockerfile for fcrepo4. The entry point script has some odd (to me) things that are causing it not to start on my system:

for MEM_FILE in memory.limit_in_bytes memory.memsw.limit_in_bytes memory.kmem.limit_in_bytes; do
  if [[ -e /sys/fs/cgroup/memory/${MEM_FILE} ]]; then
    break
  fi
done

if [[ ! -e /sys/fs/cgroup/memory/${MEM_FILE} ]]; then
  echo "Could not read container memory. Exiting."
  exit 1
fi

Just to be clear I can't run this image with plain Docker (docker run --rm -it samvera/fcrepo4:4.7.5 bash) without bypassing the entrypoint.

[dchandekstark]

The fcrepo 4 and 5 docker image tags are 3 yo, committed by @mbklein. I have a custom fcrepo4 container image that we use for a Hyrax instance, but it's a bit different: https://gitlab.oit.duke.edu/devops/containers/fcrepo4.

[tpendragon]

There may be official fcrepo images now, I know we pull official ones for Fedora 6. I'll be honest, this isn't really my strength.

[dunn]

The fcrepo 4 and 5 docker image tags are 3 yo, committed by @mbklein. I have a custom fcrepo4 container image that we use for a Hyrax instance, but it's a bit different: https://gitlab.oit.duke.edu/devops/containers/fcrepo4.

do you know where the Dockerfile for the official images are maintained? the https://github.com/fcrepo4-labs/fcrepo4-docker repository still points to the old https://hub.docker.com/r/yinlinchen/fcrepo4-docker/ image

EDIT ah, missed the link in the dockerhub page to https://github.com/nulib/docker-fcrepo