-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
make local
fails if docker
is not installed
#8055
Comments
I didn't meet this issue while building the upstream Velero release-1.14 branch code in my local environment. make local
GOOS=darwin \
GOARCH=arm64 \
GOBIN=$(pwd)/.go/bin \
VERSION=main \
REGISTRY=velero \
PKG=github.com/vmware-tanzu/velero \
BIN=velero \
GIT_SHA=cd601cafdf5d62633e252b13853b79a57138ab61 \
GIT_TREE_STATE=clean \
OUTPUT_DIR=$(pwd)/_output/bin/darwin/arm64 \
./hack/build.sh
[~/go/src/github.com/vmware-tanzu/velero] [release-1.14] |
Have you ensured you don't have any I've written down more detailed repro steps below. While docker is present, it works fine: $ git rev-parse HEAD
d9ca14747925630664c9e4f85a682b5fc356806d
$ which docker
/usr/bin/docker
$ make local
GOOS=linux \
GOARCH=amd64 \
GOBIN=$(pwd)/.go/bin \
VERSION=main \
REGISTRY=velero \
PKG=github.com/vmware-tanzu/velero \
BIN=velero \
GIT_SHA=d9ca14747925630664c9e4f85a682b5fc356806d \
GIT_TREE_STATE=clean \
OUTPUT_DIR=$(pwd)/_output/bin/linux/amd64 \
./hack/build.sh Then, after removing the docker binary from the path, it starts failing:
|
I have the same issue after removing the docker CLI in my environment. @kaovilai |
Thanks for catching that. Will get a fix up |
/assign @kaovilai |
Fixed in #8056 No longer hangs without docker in path
|
What steps did you take and what happened:
I'm usually using the velero client via the aur package. (https://aur.archlinux.org/packages/velero). Recently, the build stopped working.
(the exact same behaviour happens with just the git repo, without build as an AUR package)
What did you expect to happen:
The PKGBUILD runs make like this:
Where $pkgver is the version that is being build.
Before, builds were working no problem.
Recently, they hung forever with the following output
I've bisected this, and the first bad commit is 8f8bc9f.
Reverting just this commit makes the build work again on main.
The following information will help us better understand what's going on:
Please provide the output of the following commands
None of these are applicable, as this is a build problem
Environment:
Building on archlinux, without having the
docker
binary in the path.The text was updated successfully, but these errors were encountered: