Juju 2.7.3+ currently has this in the Makefile:
OPERATOR_IMAGE_TAG ?= $(shell ${JUJUD_BIN_DIR}/jujud version | grep -E -o "^[[:digit:]]{1,9}\.[[:digit:]]{1,9}(\.|-[[:alpha:]]+)[[:digit:]]{1,9}(\.[[:digit:]]{1,9}
)?")
# Legacy tags never have a build number.
OPERATOR_IMAGE_TAG_LEGACY ?= $(shell ${JUJUD_BIN_DIR}/jujud version | grep -E -o "^[[:digit:]]{1,9}\.[[:digit:]]{1,9}(\.|-[[:alpha:]]+)[[:digit:]]{1,9}")
However, those are evaluated with the jujud that is in your PATH, which happens long before it actually builds the jujud itself.
Which means if you are switching between 2.7 and develop, it will build an operator-image with the wrong juju version.
It also means that in a fresh Make, you end up getting a bunch of "jujud not found" error messages that look confusing.
These should really be deferred until after 'go-install' has been run.
https:/