generate-jetty-start.sh Does Not Reference Correct Path for docker-entrypoint.sh

Summary

When running /usr/local/bin/generate-jetty-start.sh, the script does not complete because it cannot find /docker-entrypoint.sh. This is because docker-entrypoint.sh is actually located in /usr/local/bin.

Steps to reproduce

1. Run the container.
2. Exec into the running container with bash, i.e.:

   docker exec -it jetty-test bash

3. Run the generate-jetty-start.sh script:

   /usr/local/bin/generate-jetty-start.sh

4. Observe the "No such file or directory" error message

What is the current bug behavior?

The script terminates with the error:

/usr/local/bin/generate-jetty-start.sh: line 8: /docker-entrypoint.sh: No such file or directory

What is the expected correct behavior?

The script runs the dry-run portion of the docker-entrypoint.sh file and outputs it to $JETTY_BASE/jetty.start.

Relevant logs and/or screenshots

bryant.murphy@x
$ docker run -d -t --name jetty-test ironbank/jetty:11.0.8
c0deb68cf8e791ed9d3521b7e8ea3e480245f6e93c69bcb13c5da041ac4c2ada

bryant.murphy@x
$ docker exec -it jetty-test bash
bash-4.4$ /usr/local/bin/generate-jetty-start.sh
/usr/local/bin/generate-jetty-start.sh: line 8: /docker-entrypoint.sh: No such file or directory

Possible fixes

Possible fix would be to change this line in generate-jetty-start.sh from:

/docker-entrypoint.sh --dry-run | sed -e 's/ -Djava.io.tmpdir=[^ ]*//g' -e 's/\\$//' > $JETTY_START

to:

/usr/local/bin/docker-entrypoint.sh --dry-run | sed -e 's/ -Djava.io.tmpdir=[^ ]*//g' -e 's/\\$//' > $JETTY_START

Tasks

• Bug has been identified and corrected within the container