-
Notifications
You must be signed in to change notification settings - Fork 220
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
Conversation
Build failed.
|
0cb1015
to
dca19b3
Compare
Build failed.
|
doc/toolbox-create.1.md
Outdated
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. |
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.
Did you really mean podman build
? Or was it meant to be podman create
?
doc/toolbox-create.1.md
Outdated
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 |
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 should definitely be podman create
. :)
doc/toolbox-list.1.md
Outdated
|
||
## 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: |
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.
Let's wait a bit before we go too much into this part, because it will be influenced by #579
dca19b3
to
1119e7f
Compare
Build succeeded.
|
- 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
1119e7f
to
f349ba0
Compare
- 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
f349ba0
to
79e7876
Compare
Fix-ups in #814 |
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.