The build and run scripts make unnecessary use of sudo.
I can see no reason why sudo is used to build the Docker file.
Presumably sudo was used to run the container because of systemd. However, it is possible to run systemd in a docker container without needing root privileges e.g.
docker run -it --stop-signal=RTMIN+3 -e "container=docker" --tmpfs /run --tmpfs /tmp -v /sys/fs/cgroup:/sys/fs/cgroup:ro --cap-add=SYS_ADMIN -p 0.0.0.0:8080:8080 shibboleth-idp
See e.g.:
https://developers.redhat.com/blog/2016/09/13/running-systemd-in-a-non-privileged-container/
moby/moby#28614 (comment)
The build and run scripts make unnecessary use of sudo.
I can see no reason why sudo is used to build the Docker file.
Presumably sudo was used to run the container because of systemd. However, it is possible to run systemd in a docker container without needing root privileges e.g.
See e.g.:
https://developers.redhat.com/blog/2016/09/13/running-systemd-in-a-non-privileged-container/
moby/moby#28614 (comment)