-
Notifications
You must be signed in to change notification settings - Fork 393
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
cluster-node-image-builder container fails in Azure pipeline #991
Comments
It's odd that the script pokes at the container, finds there is already a "cloudtest" user with UID 1001, then goes ahead and creates a "cloudtest_azpcontainer" user with the same UID. I would think "cannot lock /etc/passwd" might be an appropriate error in this case, except that the same thing happens when backed by the deis/go-dev container, and succeeds in that case. |
/assign |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
/unassign Will pick this back up once I have enough cycles |
/assign |
This failure probably arises from either the fact that the container has a non-root user and defines an Here are the general requirements for a container to be used in Azure DevOps pipelines: https://learn.microsoft.com/azure/devops/pipelines/process/container-phases?view=azure-devops#requirements |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
/priority backlog |
What steps did you take and what happened:
When running Azure image-builder tasks from this repository in pipelines, we want to use the container produced by
make -C images/capi docker-build
as recommended in the Image Builder book. But in practice it errors out, as shown in the below log.This same startup script with
useradd
runs successfully when backed by the old deis/go-dev container.What did you expect to happen:
Anything else you would like to add:
Environment:
Project (Image Builder for Cluster API, kube-deploy/imagebuilder, konfigadm):
Additional info for Image Builder for Cluster API related issues:
/etc/os-release
, orcmd /c ver
):kubectl version
):/kind bug
The text was updated successfully, but these errors were encountered: