brigade: Docker for Mac - K8s brig run - sample not working

Hi

bridge.js

const { events } = require('brigadier')

events.on("exec", (brigadeEvent, project) => {
  console.log("Hello world!")
})

With the helm inspect values brigade/brigade-project > myvalues.yaml not changes.

I have had this working on Google Kubernetes Engine, now I am trying to run this on Docker For Mac with Kubernetes.

I did install Brigade with helm install -n brigade brigade/brigade --set rbac.enabled=true

Now when I run brig run -f brigade.js deis/empty-testbed it gives me the following error:

Error: pod failed to schedule: 
Usage:
  brig run PROJECT [flags]

Flags:
  -c, --commit string    A VCS (git) commit version, tag, or branch (default "master")
  -e, --event string     The name of the event to fire (default "exec")
  -f, --file string      The JavaScript file to execute
  -p, --payload string   The path to a payload file

Global Flags:
      --kubeconfig string   The path to a KUBECONFIG file, overrides $KUBECONFIG.
  -n, --namespace string    The Kubernetes namespace for Brigade (default "default")
  -v, --verbose             Turn on verbose output

pod failed to schedule: 

I did try to brigade-worker-01c9w9q8zxj6zg8v4c39yx3d7m 0/1 Error 0 9m on the failing brigade-worker… it just returns an empty line.

kubectl describe brigade-worker-01c9w9q8zxj6zg8v4c39yx3d7m

Events:
  Type    Reason                 Age   From                         Message
  ----    ------                 ----  ----                         -------
  Normal  Scheduled              13m   default-scheduler            Successfully assigned brigade-worker-01c9w9q8zxj6zg8v4c39yx3d7m to docker-for-desktop
  Normal  SuccessfulMountVolume  13m   kubelet, docker-for-desktop  MountVolume.SetUp succeeded for volume "vcs-sidecar"
  Normal  SuccessfulMountVolume  13m   kubelet, docker-for-desktop  MountVolume.SetUp succeeded for volume "brigade-worker-token-bmsck"
  Normal  SuccessfulMountVolume  13m   kubelet, docker-for-desktop  MountVolume.SetUp succeeded for volume "brigade-build"
  Normal  Pulled                 13m   kubelet, docker-for-desktop  Container image "deis/brigade-worker:v0.11.0" already present on machine
  Normal  Created                13m   kubelet, docker-for-desktop  Created container
  Normal  Started                13m   kubelet, docker-for-desktop  Started container

Do you know why?

Thanks

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Comments: 23 (15 by maintainers)

Most upvoted comments

Some of the issues that @JCzz reports look similar to #408

@technosophos Thanks for working on this! And the only difference I spotted, is I used “kubeadm” to install my kube cluster, but not minikube. And according to it’s document, kubeadm enabled rbac by default. Not sure this matters, but that’s all I found.

And btw, I found you didn’t even install brigade with the --set rbac.enabled=true, and last time I installed without rbac, I got a lot of error vacuum pods. I searched around and enabled rbac to fixed it.

Oh, man… I am so glad you figured that out. I’m totally having zero luck getting Docker for Mac working at all. I keep running into all these little issues with the way I have my local machine set up. I should have waited longer to upgrade to Go 1.10, I think.

Sounds like I can mark this as resolved. Thanks for the details.

I’m having major problems with Docker For Mac, largely due to a problem with the way it generates SSL certificates. It sets an illegal FQDN for the cluster, and that generates errors like this:


Get https://localhost:6443/api/v1/namespaces/default/secrets?labelSelector=app%3Dbrigade%2Ccomponent%3Dproject: tls: failed to parse certificate from server: x509: cannot parse dnsName "kubernetes.default.svc."

(Note the trailing dot at the end of kubernetes.default.svc.)

Apparently a recent version of Go made it much more strict about checking this field, so I may try to revert to a version of Brigade compiled by Go 1.8 or earlier and see if I can get further.