Skip to content

Can't run custom slugbuilder #3

@Cryptophobia

Description

@Cryptophobia

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions