submariner: `make clusters` fails

What happened: Getting errors when running make clusters or make deploy as part of the getting started guide for kind.

What you expected to happen: Kind clusters should be created.

How to reproduce it (as minimally and precisely as possible): Tried both on CentOS 7.8 and macOS 11.6

Anything else we need to know?:

kubectl, subctl, docker, kind already installed properly.

CentOS output:

$ make clusters
Makefile:126: Makefile.dapper: No such file or directory
Downloading Makefile.dapper
Downloading dapper
Submariner Dapper
Downloading Dockerfile.dapper
docker network create -d bridge kind
Error response from daemon: network with name kind already exists
make: [clusters] Error 1 (ignored)
./.dapper   -- make --debug=b clusters
Sending build context to Docker daemon   9.09MB
Step 1/8 : ARG BASE_BRANCH
Step 2/8 : FROM quay.io/submariner/shipyard-dapper-base:${BASE_BRANCH}
 ---> 1a2513f0257b
Step 3/8 : ARG PROJECT
 ---> Using cache
 ---> b14ff42e2fb8
Step 4/8 : ENV DAPPER_ENV="QUAY_USERNAME QUAY_PASSWORD CLUSTERS_ARGS DEPLOY_ARGS CLEANUP_ARGS E2E_ARGS RELEASE_ARGS MAKEFLAGS FOCUS SKIP PLUGIN E2E_TESTDIR GITHUB_USER GITHUB_TOKEN"     DAPPER_SOURCE=/go/src/github.com/submariner-io/${PROJECT} DAPPER_DOCKER_SOCKET=true
 ---> Using cache
 ---> 75002b8b7e4d
Step 5/8 : ENV DAPPER_OUTPUT=${DAPPER_SOURCE}/output
 ---> Using cache
 ---> 9a74234220de
Step 6/8 : WORKDIR ${DAPPER_SOURCE}
 ---> Using cache
 ---> 48d3b8677841
Step 7/8 : ENTRYPOINT ["/opt/shipyard/scripts/entry"]
 ---> Using cache
 ---> 7c3f8ac6cc15
Step 8/8 : CMD ["sh"]
 ---> Using cache
 ---> 88b117083c88
Successfully built 88b117083c88
Successfully tagged submariner:devel
[submariner]$ trap chown -R 1001:1001 . exit
[submariner]$ mkdir -p bin dist output
[submariner]$ make --debug=b clusters
GNU Make 4.3
Built for x86_64-redhat-linux-gnu
Copyright (C) 1988-2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Reading makefiles...
make: cmp: Operation not permitted
make: /bin/bash: Operation not permitted
make: /bin/bash: Operation not permitted
make: /bin/bash: Operation not permitted
make: /bin/bash: Operation not permitted
make: /bin/bash: Operation not permitted
make: /bin/bash: Operation not permitted
make: /bin/bash: Operation not permitted
Updating makefiles....
Updating goal targets....
 File 'clusters' does not exist.
Must remake target 'clusters'.
/opt/shipyard/scripts/clusters.sh --settings /go/src/github.com/submariner-io/submariner/.shipyard.e2e.yml
make: /bin/bash: Operation not permitted
make: *** [/opt/shipyard/Makefile.inc:106: clusters] Error 127
[submariner]$ make --debug=b clusters
make: *** [clusters] Error 2

Mac output:

% make clusters
Makefile:126: Makefile.dapper: No such file or directory
Downloading Makefile.dapper
Downloading dapper
Submariner Dapper
Downloading Dockerfile.dapper
docker network create -d bridge kind
Error response from daemon: network with name kind already exists
make: [clusters] Error 1 (ignored)
./.dapper   -- make --debug=b clusters
[+] Building 10.2s (3/3) FINISHED
 => [internal] load build definition from Dockerfile.dapper                                                                                                                                        0.1s
 => => transferring dockerfile: 524B                                                                                                                                                               0.0s
 => [internal] load .dockerignore                                                                                                                                                                  0.0s
 => => transferring context: 2B                                                                                                                                                                    0.0s
 => ERROR [internal] load metadata for quay.io/submariner/shipyard-dapper-base:devel                                                                                                              10.0s
------
 > [internal] load metadata for quay.io/submariner/shipyard-dapper-base:devel:
------
failed to solve with frontend dockerfile.v0: failed to create LLB definition: failed to do request: Head https://quay.io/v2/submariner/shipyard-dapper-base/manifests/devel: Bad Gateway
sed: 1: "/"DAPPER_CP=/{s/[[:spac ...": extra characters at the end of q command
sed: 1: "/"DAPPER_ENV=/{s/[[:spa ...": extra characters at the end of q command
sed: 1: "/"DAPPER_SOURCE=/{s/[[: ...": extra characters at the end of q command
sed: 1: "/"DAPPER_DOCKER_SOCKET= ...": extra characters at the end of q command
sed: 1: "/"DAPPER_RUN_ARGS=/{s/[ ...": extra characters at the end of q command
docker: invalid reference format: repository name must be lowercase.
See 'docker run --help'.
make: *** [clusters] Error 125

Environment:

  • Diagnose information (use subctl diagnose all):
  • Gather information (use subctl gather):
  • Cloud provider or hardware configuration:
  • Install tools:
  • Others:

Would be helpful also to have docs on what is the required configuration for kind clusters when running kind CLI manually not using make file? (CIDRs, CNI, nodes, etc…) Tried also to setup kind clusters manually with non-overlapping CIDRs but gateways on both clusters cannot connect. Pardon if this bug report is due to a newcomer’s mistake.

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 23 (20 by maintainers)

Most upvoted comments

Is this still being worked on? I don’t see any such issues with my Fedora 35 system, but not sure about other OSs.

Yes, I’m still working on this.