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

WIP: Vendor https://github.com/containers/storage/pull/473 for testing #5706

Closed
wants to merge 1 commit into from

Conversation

saschagrunert
Copy link
Member

To verify that containers/storage#473 works (or not)

@rhatdan
Copy link
Member

rhatdan commented Apr 3, 2020

#5700 Should help fix this.

@TomSweeneyRedHat
Copy link
Member

@saschagrunert looks like some lint errors in the unshare package.

@rh-atomic-bot
Copy link
Collaborator

☔ The latest upstream changes (presumably #5700) made this pull request unmergeable. Please resolve the merge conflicts.

@rhatdan
Copy link
Member

rhatdan commented Apr 3, 2020

Rebase and this should at least compile now.

@openshift-ci-robot openshift-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Apr 3, 2020
@saschagrunert
Copy link
Member Author

Rebased on top of the latest master.

@openshift-ci-robot openshift-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Apr 6, 2020
@rh-atomic-bot
Copy link
Collaborator

☔ The latest upstream changes (presumably #5727) made this pull request unmergeable. Please resolve the merge conflicts.

@rhatdan
Copy link
Member

rhatdan commented Apr 6, 2020

@saschagrunert Needs a rebase again.

@openshift-ci-robot openshift-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Apr 7, 2020
@openshift-ci-robot openshift-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Apr 7, 2020
@saschagrunert saschagrunert force-pushed the vendor-ro-mod branch 2 times, most recently from a5433f4 to c973ac8 Compare April 7, 2020 09:25
@saschagrunert
Copy link
Member Author

Hm this issue does not seem reproducible locally to me:

Error: error committing container for step {Env:[PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin] Command:run Args:[apk add bash] Flags:[] Attrs:map[] Message:RUN apk add bash Original:RUN apk add bash}: error copying layers and metadata for container "e1d34b849fc5ef59630cebd2a5a7d146604e09db3de35e40d41e4d94c68f69a3": Error reading blob sha256:c82ab33dce84c975f00a42224fa2914b27a943c1175175f67483f4eebdaaf198: error opening file "/var/tmp/buildah155921171/sha256:c82ab33dce84c975f00a42224fa2914b27a943c1175175f67483f4eebdaaf198" to buffer layer blob: open /var/tmp/buildah155921171/sha256:c82ab33dce84c975f00a42224fa2914b27a943c1175175f67483f4eebdaaf198: no such file or directory

@saschagrunert saschagrunert force-pushed the vendor-ro-mod branch 6 times, most recently from e668504 to 302d147 Compare April 15, 2020 13:06
@rhatdan
Copy link
Member

rhatdan commented Apr 15, 2020

@giuseppe PTAL

@saschagrunert
Copy link
Member Author

This PR should be green now with the latest changes in containers/storage#473

@saschagrunert
Copy link
Member Author

saschagrunert commented Apr 15, 2020

Look how partially green! :)

@github-actions
Copy link

A friendly reminder that this PR had no activity for 30 days.

@rhatdan
Copy link
Member

rhatdan commented May 16, 2020

@saschagrunert Are you getting back to this one?

@saschagrunert
Copy link
Member Author

@rhatdan yes, can we move forward with the related PR in containers/storage? (containers/storage#473)

@rhatdan
Copy link
Member

rhatdan commented Aug 3, 2020

@saschagrunert Could you update this PR to prove that the containers/storage PR still works?

@saschagrunert
Copy link
Member Author

Rebased the referencing PR as well as this one on top of their latest master branches. 👍

@rhatdan rhatdan removed the stale-pr label Aug 4, 2020
@saschagrunert
Copy link
Member Author

Sooo there seems to be an issue now…

@openshift-ci-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: saschagrunert
To complete the pull request process, please assign mrunalp
You can assign the PR to them by writing /assign @mrunalp in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@saschagrunert
Copy link
Member Author

Hmmm…

[+0331s] not ok 50 podman exec - with keep-id
         # (from function `die' in file test/system/helpers.bash, line 287,
         #  from function `run_podman' in file test/system/helpers.bash, line 170,
         #  in test file test/system/075-exec.bats, line 105)
         #   `run_podman exec --user=$(id -un) $cid touch /stop' failed with status 255
         # # podman rm --all --force
         # # podman images --all --format {{.Repository}}:{{.Tag}} {{.ID}}
         # quay.io/libpod/alpine_labels:latest 4fab981df737
         # # podman run -d --userns=keep-id quay.io/libpod/alpine_labels:latest sh -c echo READY;while [ ! -f /stop ]; do sleep 1; done
         # 396f4537b154ca0d86d607a66f7520c88e271d3619a2b0d2ddeedcaac4d1db2b
         # # podman logs 396f4537b154ca0d86d607a66f7520c88e271d3619a2b0d2ddeedcaac4d1db2b
         # READY
         # # podman exec 396f4537b154ca0d86d607a66f7520c88e271d3619a2b0d2ddeedcaac4d1db2b id -un
         # root
         # # podman exec --user=root 396f4537b154ca0d86d607a66f7520c88e271d3619a2b0d2ddeedcaac4d1db2b touch /stop
         # Error: unable to find user root: no matching entries in passwd file
         # [ rc=255 (** EXPECTED 0 **) ]
         # #/vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
         # #| FAIL: exit code is 255; expected 0
         # #\^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
         # # [teardown]
         # # podman pod rm --all --force
         # # podman rm --all --force
         # 396f4537b154ca0d86d607a66f7520c88e271d3619a2b0d2ddeedcaac4d1db2b

@saschagrunert saschagrunert force-pushed the vendor-ro-mod branch 2 times, most recently from 0f0329b to 37cda2f Compare August 28, 2020 10:10
@rhatdan
Copy link
Member

rhatdan commented Sep 11, 2020

@saschagrunert Please rebase this PR.

@saschagrunert
Copy link
Member Author

I've switched forks, continuing in a new PR: #7603

@saschagrunert saschagrunert deleted the vendor-ro-mod branch September 11, 2020 11:52
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 24, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 24, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants