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

Why task is downloading aditional code? #3

Closed
piterzet opened this issue Dec 1, 2022 · 2 comments
Closed

Why task is downloading aditional code? #3

piterzet opened this issue Dec 1, 2022 · 2 comments
Assignees

Comments

@piterzet
Copy link

piterzet commented Dec 1, 2022

I run this task as a step within a pipeline which is using self-hosted agent (Ubuntu). Task crashes with log:

Unable to run provided bash command '(
curl -sSL "https://github.com/buildpacks/pack/releases/download/v0.27.0/pack-v0.27.0-linux.tgz" | tar -C /usr/local/bin/ --no-same-owner -xzv pack)'.
##[error]Unable to install pack CLI.
##[error]The process '/bin/bash' failed with exit code 2

After digging to your code I saw this.

Don't understand why it was done this way and I don't like this.
IMHO please add prerequisites entry about Cloud Native Buildpacks and in your code just check if package is aviable.

@cormacpayne
Copy link
Member

@piterzet Hey there -- apologies for the delayed response; this is a good call-out. We use Cloud Native Buildpacks to produce a runnable application image within the task for the user if they don't provide a Dockerfile to build or a previously built and push image, but we need to install the pack CLI for CNB in order to do so, which is what the script you mentioned above does. This should be called out in the prerequisites of the task so users know why the pack CLI is being installed, as well as a check for the CLI when the task is executing to determine whether or not we need to install it. Thanks for the report!

@cormacpayne
Copy link
Member

@piterzet Hey there -- this issue is resolved in the latest release of the AzureContainerAppsRC task (0.1.8). Please feel free to let us know if there's anything else that you'd like for us to address with this issue in the future. Thanks!

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

2 participants