Skip to content
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

Can't run custom slugbuilder #3

Open
Cryptophobia opened this issue Mar 13, 2018 · 0 comments
Open

Can't run custom slugbuilder #3

Cryptophobia opened this issue Mar 13, 2018 · 0 comments

Comments

@Cryptophobia
Copy link
Member

From @szymonpk on February 23, 2017 10:7

I'm trying to run custom slugbuilder image on my cluster, I'm following this doc and advices from slack. For now I'm trying plain unmodified slugbuilder code.

Steps to reproduce:

  1. Env and build process:

     export DEIS_REGISTRY=quay.io/
     export IMAGE_PREFIX=szymon_szypulski
     make deploy
    

    Image is pushed succesfully and tagged as cannary.

  2. kubectl edit configmap slugbuilder-config -n deis. I'm changing image to quay.io/szymon_szypulski/slugbuilder:canary, pullpolicy to Always.

  3. I'm deleting currently running builder pod, it is recreated successfully.

  4. Pushing the app, build fails.

  5. kubect describe pod <slugbuilder_app_pod_name> -n deis shows:

     State:              Terminated
       Reason:           Error
       Exit Code:        126
    
  6. kubectl logs pod <slugbuilder_app_pod_name> -n deis` shows:

     /usr/bin/env: bash: Permission denied
    

I've tried minikube and vagrant based cluster.

I'm pretty sure I'm doing something wrong, but I'm not sure what :/ I assume, official images are built same way.

Copied from original issue: deis/slugbuilder#133

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant