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

doc: Match man pages with Go Toolbox and extend them #512

Merged
merged 1 commit into from
May 24, 2021

Conversation

HarryMichal
Copy link
Member

@HarryMichal HarryMichal commented Jul 23, 2020

The manual pages were not updated for quite some time already. Several parts are not relevant anymore (e.g., mentions of 'candidate registry') and some could be more accurate/more elaborate.

I mainly expanded toolbox(1), toolbox-create(1) and toolbox-init-container(1) where I tried to explain more of the philosophy of toolbox containers/images, what defines them, what makes them different than common OCI containers/images.

@HarryMichal HarryMichal added this to the Release 0.1.0 milestone Jul 23, 2020
@softwarefactory-project-zuul
Copy link

Build failed.

@HarryMichal HarryMichal force-pushed the extend-manual-pages branch from 0cb1015 to dca19b3 Compare July 24, 2020 10:44
@HarryMichal HarryMichal marked this pull request as ready for review July 24, 2020 10:44
@HarryMichal HarryMichal requested a review from debarshiray July 24, 2020 10:44
@softwarefactory-project-zuul
Copy link

Build failed.

doc/toolbox-create.1.md Outdated Show resolved Hide resolved
locally customized for the current user to create a second image, from which
the container is finally created.
A toolbox container is an OCI container created from an OCI image. Therefore,
`toolbox create` is analogous to `podman build` executed with specific options.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did you really mean podman build? Or was it meant to be podman create?

Toolbox containers are primarily created in a way to be tightly integrated with
the host system. They are not meant to be secure.

### Options passed to podman build
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should definitely be podman create. :)

doc/toolbox-create.1.md Outdated Show resolved Hide resolved
doc/toolbox-create.1.md Outdated Show resolved Hide resolved
doc/toolbox-init-container.1.md Outdated Show resolved Hide resolved

## DESCRIPTION

Lists existing toolbox containers and images. These are OCI containers and
images, which can be managed directly with tools like `buildah` and `podman`.

Listed information about images:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's wait a bit before we go too much into this part, because it will be influenced by #579

doc/toolbox-enter.1.md Outdated Show resolved Hide resolved
doc/toolbox-enter.1.md Outdated Show resolved Hide resolved
@softwarefactory-project-zuul
Copy link

Build succeeded.

@HarryMichal HarryMichal requested a review from debarshiray March 4, 2021 21:41
@HarryMichal HarryMichal added the 2. Documentation The issue is related to the user documentation label Mar 4, 2021
Base automatically changed from master to main March 25, 2021 22:25
HarryMichal added a commit to HarryMichal/toolbox that referenced this pull request May 24, 2021
- Update "See also" sections

Toolbox does not use Buildah for a considerable time now[0]. We can stop
referencing it in the "See also" sections of the documentation.

In some places mention podman command man pages where they are relevant.

- Add section about toolbox images/containers

Toolbox only supports certain OCI images. These should be documented.
Also, document the change of fedora-toolbox image name.

- Add a section about toolbox container setup

Toolbox containers are specifically configured OCI containers. This
should be documented so that users know what they're using.

- Remove redundant part documentation

The description of what `toolbox init-container` does is already in
toolbox-init-container(1). There's no need to have it in
toolbox-create(1). Instead, replace the text with a hint to visit the
other part of documentation.

- Clarify behaviour of --image option

The fact that Toolbox by default tries to pull from the Fedora
registry[1] should be noted.

- Update synopsis & description of commands

Mention options passed to `podman exec`. Remove redundant paragraph
about container names (is already dealt with in toolbox-create(1)).

There's no need to mention the name of the default container on Fedora
since Toolbox now also supports RHEL.

Mention the default used image on unrecognised systems.

Emphasize the fact that toolboxes are not a fully sandboxed environment.

Update the wording of the description and splits it into a few
subsections.

The description of the --monitor-host was inaccurate and while the
option will go away in the future[2], it is currently in and should be
more documented.

[0] containers#160
[1] https://registry.fedoraproject.org
[2] containers#617

containers#512
@HarryMichal HarryMichal force-pushed the extend-manual-pages branch from 1119e7f to f349ba0 Compare May 24, 2021 15:10
- Update "See also" sections

Toolbox does not use Buildah for a considerable time now[0]. We can stop
referencing it in the "See also" sections of the documentation.

In some places mention podman command man pages where they are relevant.

- Add section about toolbox images/containers

Toolbox only supports certain OCI images. These should be documented.
Also, document the change of fedora-toolbox image name.

- Add a section about toolbox container setup

Toolbox containers are specifically configured OCI containers. This
should be documented so that users know what they're using.

- Remove redundant part documentation

The description of what `toolbox init-container` does is already in
toolbox-init-container(1). There's no need to have it in
toolbox-create(1). Instead, replace the text with a hint to visit the
other part of documentation.

- Clarify behaviour of --image option

The fact that Toolbox by default tries to pull from the Fedora
registry[1] should be noted.

- Update synopsis & description of commands

Mention options passed to `podman exec`. Remove redundant paragraph
about container names (is already dealt with in toolbox-create(1)).

There's no need to mention the name of the default container on Fedora
since Toolbox now also supports RHEL.

Mention the default used image on unrecognised systems.

Emphasize the fact that toolboxes are not a fully sandboxed environment.

Update the wording of the description and splits it into a few
subsections.

The description of the --monitor-host was inaccurate and while the
option will go away in the future[2], it is currently in and should be
more documented.

[0] containers#160
[1] https://registry.fedoraproject.org
[2] containers#617

containers#512
@HarryMichal HarryMichal force-pushed the extend-manual-pages branch from f349ba0 to 79e7876 Compare May 24, 2021 15:13
@HarryMichal HarryMichal merged commit ea452d7 into containers:main May 24, 2021
@HarryMichal HarryMichal deleted the extend-manual-pages branch May 24, 2021 15:15
doc/toolbox-create.1.md Show resolved Hide resolved
doc/toolbox-create.1.md Show resolved Hide resolved
doc/toolbox-create.1.md Show resolved Hide resolved
doc/toolbox-init-container.1.md Show resolved Hide resolved
doc/toolbox-create.1.md Show resolved Hide resolved
doc/toolbox-create.1.md Show resolved Hide resolved
doc/toolbox-enter.1.md Show resolved Hide resolved
doc/toolbox-init-container.1.md Show resolved Hide resolved
doc/toolbox-init-container.1.md Show resolved Hide resolved
doc/toolbox-init-container.1.md Show resolved Hide resolved
@debarshiray
Copy link
Member

Fix-ups in #814

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2. Documentation The issue is related to the user documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants