COPY failed: stat /var/lib/docker/tmp/docker-builderxxxxxxxxx/tools: no such file or directory about keycloak-operator

[JiyeYu]

I checked build/Dockerfiles and found the possible errors.
In build/Dockerfiles, line 21/24, which are doing the COPY job, the path is not correct.
They should be
COPY build/tools /opt/jboss/tools and
COPY build/bin /usr/local/bin
After these two changes, I passed the image build.

[JiyeYu]

I found this commit: 940e73d

In this commit, copy directory is changed from build/bin to bin on purpose.
Seems you are doing the docker build in build folder? Not by operator-sdk build from the root directory of this project.

Then in readme.md, https://github.com/keycloak/keycloak-operator#alternative-step-3-deploying-to-a-cluster, step:
build image with operator-sdk build <image registry>/<organisation>/keycloak-operator:<tag>. e.g. operator-sdk build quay.io/keycloak/keycloak-operator:test would be failed as this issue shows. 🤔

[abstractj]

I found this commit: 940e73d

In this commit, copy directory is changed from build/bin to bin on purpose.
Seems you are doing the docker build in build folder? Not by operator-sdk build from the root directory of this project.

Then in readme.md, https://github.com/keycloak/keycloak-operator#alternative-step-3-deploying-to-a-cluster, step:
build image with operator-sdk build <image registry>/<organisation>/keycloak-operator:<tag>. e.g. operator-sdk build quay.io/keycloak/keycloak-operator:test would be failed as this issue shows.

@JiyeYu thanks for reporting this. Even though we understand that it's a common practice to use operator-sdk to build new images, we could not find any efficient way to trigger the build with operator-sdk from quay.io, so that's the reason why we use Docker. So to build the operator just run:

docker build --no-cache -t ${NAMESPACE}/${PROJECT}:${VERSION} -f build/Dockerfile

At the moment this is how it works. I will update the readme to reflect these instructions.

Please feel free to reopen this issue if I didn't answer your question.

[JiyeYu]

@abstractj thank you for your answer. Now I understand your intention on that change.