Pre-loading container images into CRI-O#568
Conversation
0a6baa1 to
c907eaf
Compare
c907eaf to
909e97e
Compare
a1df000 to
8e44116
Compare
acbd9a0 to
d6316a5
Compare
|
/retest |
|
/retest |
d49d49f to
916b3c4
Compare
|
@fzdarsky please TAL |
| Release: 1 | ||
| # this can be %{timestamp}.git%{short_hash} later for continous main builds | ||
| Summary: Create custom container storage | ||
| License: ASL 2.0 |
There was a problem hiding this comment.
Is ASL the correct abbreviation (as it's Apache License not Apache Software Licence or such?
There was a problem hiding this comment.
ASL is Apache Software License. Going to change it to AL 2.0
| %build | ||
|
|
||
|
|
||
| %install |
There was a problem hiding this comment.
Shouldn't this belong into the %build section, such that the RPM contains the images (rather than pulling them when installed)? Not sure the ImageBuilder can actually run stuff on podman when building ostrees.
There was a problem hiding this comment.
As per the doc, https://rpm-packaging-guide.github.io/#what-is-a-spec-file
%build: Command or series of commands for actually building the software into machine code (for compiled languages) or byte code (for some interpreted languages).
%Install: Command or series of commands for copying the desired build artifacts from the %builddir (where the build happens) to the %buildroot directory (which contains the directory structure with the files to be packaged). This usually means copying files from ~/rpmbuild/BUILD to ~/rpmbuild/BUILDROOT and creating the necessary directories in ~/rpmbuild/BUILDROOT. This is only run when creating a package, not when the end-user installs the package. See [Working with SPEC files](https://rpm-packaging-guide.github.io/#working-with-spec-files) for details.
Since we are not building s/w and only using rpm to package files, I put it under %install
There was a problem hiding this comment.
it's .spec files just being confusing,
What you expect for install is %post
%install is the phase that takes the %build, and put's it into the fake root filesystem,
from where %file will gather stuff.
Signed-off-by: Parul <parsingh@redhat.com>
Signed-off-by: Parul <parsingh@redhat.com>
Signed-off-by: Parul <parsingh@redhat.com>
Signed-off-by: Miguel Angel Ajo <majopela@redhat.com>
|
@mangelajo @fzdarsky |
|
|
||
| #Generate microshift-app-images.spec | ||
| touch ./microshift-app-images.spec | ||
| cat >./microshift-app-images.spec <<EOF |
There was a problem hiding this comment.
We should probably propagate the changes from the other spec here.
But I propose we merge, and then we keep working on the userland side.
There was a problem hiding this comment.
@mangelajo good idea. Could you open an issue for that please so we don't forget?
| URL: https://github.com/redhat-et/microshift | ||
|
|
||
| BuildRequires: podman | ||
| BuildRequires: crio |
There was a problem hiding this comment.
| BuildRequires: crio | |
| Requires: crio |
|
#611 |
Signed-off-by: Parul <parsingh@redhat.com>
|
@husky-parul: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
|
/lgtm |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fzdarsky, mangelajo The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Signed-off-by: Parul parsingh@redhat.com
Which issue(s) this PR addresses:
Pre-loading container images into CRI-O
Closes #
#162
Should be merged after #593