Documentation for general installation in containerized environments

[me-coder]

The CFEngine installation guide is missing out on containers.
This PR is an attempt to project the capability of CFEngine with containers (using ubi9-init images).

There are a few limitations due to the nature of CFEngine (requires privileged mode and container is required to have systemd, which need initialization with /var/sbin/init).
However, it still gives a good ability to test CFEngine in containerized environments in full capacity, without the need to have a bulky multi VM setup.

Hope the moderator team finds this useful and decides to integrate it into the docs.

[me-coder]

I am unable to figure out the reason for failure of check with:
Run markdowner.py on all markdown files and see if there are changes / check (pull_request)

Any help to deal with this cryptic error is appreciated.

[olehermanse]

I am unable to figure out the reason for failure of check with:
Run markdowner.py on all markdown files and see if there are changes / check (pull_request)

Any help to deal with this cryptic error is appreciated.

Your files have extra spaces in them, at the ends of multiple lines.
Change your editor to automatically trim trailing whitespace for you, or run the command as suggested;

python3 .github/workflows/markdowner.py ./getting-started/installation/general-installation/installation-community-containerized.markdown

That will edit the file, removing those extra unnecessary spaces.
(Afterwards you will need to add and commit those changes - git add -p ; git commit).

[me-coder]

I am unable to figure out the reason for failure of check with:
Run markdowner.py on all markdown files and see if there are changes / check (pull_request)

Any help to deal with this cryptic error is appreciated.

Your files have extra spaces in them, at the ends of multiple lines. Change your editor to automatically trim trailing whitespace for you, or run the command as suggested;

python3 .github/workflows/markdowner.py ./getting-started/installation/general-installation/installation-community-containerized.markdown

That will edit the file, removing those extra unnecessary spaces. (Afterwards you will need to add and commit those changes - git add -p ; git commit).

The extra spaces (particularly ^.+<space><space>$ was required for newline as per the markdown requirements.
However, that has been replaced by </br> now and seems to have worked.
Thanks for the suggestion.

[me-coder]

@olehermanse,
I've made this change to take care of such situations, if encountered by other contributors:
c9719c9

Hope that's fine.

[olehermanse]

The extra spaces (particularly ^.+$ was required for newline as per the markdown requirements.

What requirements? This is not required.

However, that has been replaced by
now and seems to have worked.

No, remove these, they are not necessary.

I've made this change to take care of such situations, if encountered by other contributors:
c9719c9

Hope that's fine.

No, that change is not correct, remove it. We want to strip trailing whitespace. You don't need trailing whitespace nor html tags (</br>) to write this tutorial.

[nickanderson]

@me-coder thank you for this contribution. Overall it's quite a nice addition. Looking forward to having this in the docs.

[nickanderson]

@olehermanse Perhaps this should be re-titled to Installing Enterprise using disk image Or actually, maybe we need to drop this page completely. I don't see that we are still publishing a disk image since CoreOS is died (and now it's resurrected under Fedora https://fedoraproject.org/coreos/ ).

[me-coder]

@nickanderson, it seems GitHub expects this review comment to be resolved for the review to be marked complete.
The link against requested change #3355 (review) which doesn't seem like the issue.

Can this be reconsidered?

[nickanderson]

Hi @me-coder I don't think it's because of this comment, just the other comments and suggestions in general where my review was set for requested changes.

Anyway, this comment had nothing to do with your PR. I just need to re-review.

[me-coder]

Hi @olehermanse, @nickanderson,
Thank you for the detailed review.

I made the suggested changes and also a few enhancements to the document and force pushed it as a amended single commit.
I'm not sure if the suggested commits were supposed to be incorporated or were just markers for the review suggestions. (unaware of the rules being followed for this project).

I submitted a single commit as I always feel it's cleaner, could be fast-forwarded and there were changes which I could easily edit as a batch in VSCode editor.

Kindly re-consider the review with the applied changes.

- @me-coder

Changes have been made, and re-review is needed.

[nickanderson]

I am traveling and I likely won't get around to looking at this again until next week at the very earliest if I manage to catch up with other things after travel.

[me-coder]

Hi @nickanderson , @olehermanse, @craigcomstock,
Could you revisit the review?