Optimized Docker image (modified Dockerfile)

[ghrlgv]

As I have limited compute and storage resources, I use docker when possible.

The included original Dockerfile creates an image that builds the java executable when running the image (starting the app container) and includes the full JDK environment. The following Dockerfile generates a image that is half the size, includes only a runtime version of java (jre), uses a slim Debian base image and doesn't create the java executable when the container is started. Hence, it uses less resources and is speedier.

Feel free to use the attached Dockerfile and adjust it as needed (rename it to Dockerfile and use docker compose build).

Dockerfile.txt

[juherr]

@ghrlgv You should be able to remove the COPY instruction for the classes, as they are already packaged in the WAR file. This should simplify the image and avoid unnecessary duplication.

[goekay]

As I have limited compute and storage resources ...

could you elaborate what kind of environment you are running steve on? how limited are these resources?

[ghrlgv]

As I have limited compute and storage resources ...

could you elaborate what kind of environment you are running steve on? how limited are these resources?

I'm running steve on a Synology NAS DS916+, which has an Intel N3710 CPU with 4 cores at 1.6 GHz and 8 GB RAM and obvious lot's of storage. I'm using steve to manage a private EV charger that I build using a Stegen Electronics Smart EVSE module (BTW I have no connection to the Stegen company whatsoever.)

[goekay]

thank you. there was another recent issue from someone saying that they run steve on a PI.

apparently, there is a non-empty user base who use steve on restricted resources. this is important input for me to plan the future of the project.