The target build folder can cache between runs and can also get confused when mounted in a container or if you run on the machine operating system. We therefore, remove the target folder when building the docker image or generating the bindings.
The Dockerfile has had its verbosity reduced by excluding the output of apk, tar and wget. The RUN commands have also been consolidated to reduce layers and image size. Although, this is strictly not that important, for a build image.
@negezor - this is a replacement PR for #72 which unfortunately has the issue with an included chore release. Hopefully, doing the work in this one will make up for requesting you to correct #72.
Note: Using a fork to test the actions in the forked repo to ensure that they do not introduce released files.
The target build folder can cache between runs and can also get confused when mounted in a container or if you run on the machine operating system. We therefore, remove the target folder when building the docker image or generating the bindings.
The Dockerfile has had its verbosity reduced by excluding the output of
apk
,tar
andwget
. TheRUN
commands have also been consolidated to reduce layers and image size. Although, this is strictly not that important, for a build image.@negezor - this is a replacement PR for #72 which unfortunately has the issue with an included chore release. Hopefully, doing the work in this one will make up for requesting you to correct #72.
Note: Using a fork to test the actions in the forked repo to ensure that they do not introduce released files.