-
Notifications
You must be signed in to change notification settings - Fork 53
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
Add packages and update docs #324
Conversation
31e8d7c
to
032bbbb
Compare
31141fe
to
32d4c84
Compare
I can't test the "from scratch" example above without a published change of cOS that is in this PR, I will amend in case it's not working in a follow-up. I need another round to consume gomplate in any case. |
32d4c84
to
1778988
Compare
ENV LUET_NOLOCK=true | ||
SHELL ["/usr/bin/luet", "install", "-y", "-d"] | ||
|
||
RUN system/cos |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is the one I couldn't test till the end. It fails during install because /etc/hostname
is already populated by docker
@@ -108,3 +108,9 @@ excludes: | |||
- ^/usr/local/share | |||
- ^/usr/local/src | |||
- ^/usr/local/games | |||
|
|||
- ^/etc/hostname |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've added those to excludes. Hostname is generated by docker, so not really needed, similarly for the rest.
9615bf9
to
90a2e4f
Compare
We are using it for generating CI pipelines, handy to have directly in our repository Signed-off-by: Ettore Di Giacinto <[email protected]>
This will allow us to free any dependency on the luet-lab/luet-repo repository Signed-off-by: Ettore Di Giacinto <[email protected]>
Fixes #274 Fixes #275 Signed-off-by: Ettore Di Giacinto <[email protected]>
Signed-off-by: Ettore Di Giacinto <[email protected]>
Signed-off-by: Ettore Di Giacinto <[email protected]>
Signed-off-by: Ettore Di Giacinto <[email protected]>
90a2e4f
to
f057ff8
Compare
|
||
4. Followed the procedure described in [AWS docs](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/creating-an-ami-ebs.html#creating-launching-ami-from-snapshot) to register an AMI from snapshot. Used all default settings unless for the firmware, were I forced it to UEFI boot. | ||
|
||
5. Launch instance with this simple userdata: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this really needed? I booted the instance with a different user data, not creating users and root/cos was available.
Also, what is really needed if you want to launch the raw image is to provide a layout file (like in the example user-data) so its possible to use the new cos-deploy to install the system.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good point! I'll update the docs 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done!
Signed-off-by: Ettore Di Giacinto <[email protected]>
bd25848
to
7d05aec
Compare
* Keep working dir after a chroot call Signed-off-by: David Cassany <[email protected]>
This PR is multi-fold:
gomplate
as we now use it to generate CI pipelinesrancherd
luet-makeiso
to our tree. Once it gets published, we can consume it in https://github.com/rancher-sandbox/cOS-toolkit/blob/master/scripts/get_luet.sh and drop the dependency of the official luet-repo repository.cOS
during upgrades. This encompasses key concepts over https://github.com/ibuildthecloud/os2 while providing also examples.PR is draft as I need to test the examples provided first