search

openshift / pipelines-tutorial

A step-by-step tutorial showing OpenShift Pipelines
Apache License 2.0
298 stars 621 forks source link

Error while running pipeline - couldn't determine what "/var/lib/containers/.../merged is" #83

Closed gasgithub closed 3 years ago

gasgithub commented 4 years ago

Hi,

I'm trying pipeline tutorial, just changed the repo and Dockerfile. All resources created, when I run pipeline I'm hitting the following error:

Any hints what might be wrong? Here is pipeline and the Dockerfile

tkn pipelinerun logs build-and-deploy-run-hq4lz -f

[build-image : git-source-app-repo-qh8fd] {"level":"info","ts":1589824315.4050386,"caller":"git/git.go:105","msg":"Successfully cloned http://github.com/gasgithub/get-started-java.git @ master in path /workspace/source"}
[build-image : git-source-app-repo-qh8fd] {"level":"warn","ts":1589824315.4058552,"caller":"git/git.go:152","msg":"Unexpected error: creating symlink: symlink /tekton/home/.ssh /root/.ssh: file exists"}
[build-image : git-source-app-repo-qh8fd] {"level":"info","ts":1589824315.5597413,"caller":"git/git.go:133","msg":"Successfully initialized and updated submodules in path /workspace/source"}

[build-image : build] [STEP 1: FROM ibmcom/websphere-liberty:kernel-java8-ibmjava-ubi
[build-image : build] [Getting image source signatures
[build-image : build] [Copying blob sha256:58e1deb9693dfb1704ccce2f1cf0e4d663ac77098a7a0f699708a71549cbd924
...
[build-image : build] [0mCopying config sha256:25b630d683bb524a292779ef58d2200da5eda80ffe6f94652b91ac0ba16a202d
[[build-image : build] [Writing manifest to image destination
[[build-image : build] [Storing signatures
[[build-image : build] [STEP 2: COPY --chown=1001:0  target/GetStartedJava.war /config/apps/
[[build-image : build] [error dry-running "COPY --chown=1001:0  target/GetStartedJava.war /config/apps/": couldn't determine what "/var/lib/containers/storage/overlay/86fe61b71cde8535b700d3faaa10cb54715c976f1c3792ecc85623e0c614ba97/merged" is: stat /var/lib/containers/storage/overlay/86fe61b71cde8535b700d3faaa10cb54715c976f1c3792ecc85623e0c614ba97/merged: invalid argument

[mfailed to get logs for task build-image : container step-build has failed  : [{"key":"StartedAt","value":"2020-05-18T17:51:55Z","resourceRef":{}}]
gasgithub commented 4 years ago

Unfortunately same error with tutorial UI project:

step-build
STEP 1: FROM python:3.7-alpine
Getting image source signatures
Copying blob sha256:a3916b494c8f7f35e3114e0ea5aad570c15225d0fc7b0283f3c32e590771a128
Copying blob sha256:26ebcd19a4e3221ee54d309346df0869af0d74a25920287f70b0ee1da1bf75de
Copying blob sha256:038cfaa9de84da577b2d98f03ae51c51dcc92fce84d08a9db1df08bc5917e845
Copying blob sha256:f2a4afa74df82dfc5ab95c31577b88e6ba1b754beeb86ff688d264a904aa0898
Copying blob sha256:cbdbe7a5bc2a134ca8ec91be58565ec07d037386d1f1d8385412d224deafca08
Copying config sha256:61681f5202041de441532b386c74adbf0e81ed433eb79581c12c817a12ef609b
Writing manifest to image destination
Storing signatures
STEP 2: WORKDIR /app
error building at STEP "WORKDIR /app": error ensuring container path "/app": lstat /var/lib/containers/storage/overlay/e5dba4e2b8da6e2790b92468f66bd9669cbc31b8aa1571ae07e06082bfa860df/merged/app: invalid argument
nastacio commented 4 years ago

Likely this: https://github.com/containers/buildah/issues/2198

YukiGibson commented 4 years ago

Just tested what nastacio shared and it worked. Thanks! Adding '--storage-driver=vfs' to buildah in Pipelines/Cluster Tasks indeed works.

Another way to make this work, is to add '--storage-driver=overlay' under both build and push. I tested for a while and this actually worked for me.

openshift-bot commented 3 years ago

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

openshift-bot commented 3 years ago

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten /remove-lifecycle stale

openshift-bot commented 3 years ago

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen. Mark the issue as fresh by commenting /remove-lifecycle rotten. Exclude this issue from closing again by commenting /lifecycle frozen.

/close

openshift-ci-robot commented 3 years ago

@openshift-bot: Closing this issue.

In response to [this](https://github.com/openshift/pipelines-tutorial/issues/83#issuecomment-748907351): >Rotten issues close after 30d of inactivity. > >Reopen the issue by commenting `/reopen`. >Mark the issue as fresh by commenting `/remove-lifecycle rotten`. >Exclude this issue from closing again by commenting `/lifecycle frozen`. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.