There are a few constraints to note however:
Sadly, the way bazel sandboxes things puts some limitations on
what rules can be included where. The general rule is, if you have a
build rule in a directory X you can mention only rules that
are in X itself, or a subdirectory of X, like
X/dir, or X/dir1/dir2. It is not possible to
refer to X/dir1:rule from
X/dir2:rule.
The build rules pull the container filipfilmar/ebook-buildenv from the Internet. While I know what is inside (and you can check the intended contents in docker/), it’s still your build system downloading random stuff from the Internet and running on your machine. This may be OK for you to the extent that you trust me to provide you with the software that I tell you I’m providing.
In case this doesn’t fulfill your trust criteria, you are of course free to fork this repository, and use your own buildenv, since all the recipes are there.
Another possibility, which has been left for some future, is to add the container build and upload recipes to these rules, so that you can choose to build and use your own container easily.
As currently written, the rules probably only work on Linux, which is the same platform as my dev box. It should in principle be possible to rig the build rules so that they do the correct thing cross-platform, but I don’t have an immediate plan to do so, as long as the rules satisfy my own needs.