summaryrefslogtreecommitdiff
path: root/system/buildah
diff options
context:
space:
mode:
authorB. Watson <yalhcru@gmail.com>2022-03-14 12:00:41 -0400
committerB. Watson <yalhcru@gmail.com>2022-03-17 12:38:03 -0400
commitd05bd2c247ae0a4649bba2938b18f8df4ae5fc34 (patch)
tree055bf8fa29dcca67d14cf9853dbf1e9ccb63ac78 /system/buildah
parent40553bb736a8e061bd9660b4617852f270b54045 (diff)
downloadslackbuilds-d05bd2c247ae0a4649bba2938b18f8df4ae5fc34.tar.gz
system/buildah: Wrap README at 72 columns.
Signed-off-by: B. Watson <yalhcru@gmail.com>
Diffstat (limited to 'system/buildah')
-rw-r--r--system/buildah/README21
1 files changed, 11 insertions, 10 deletions
diff --git a/system/buildah/README b/system/buildah/README
index 75d3214ce2..4c09600eb9 100644
--- a/system/buildah/README
+++ b/system/buildah/README
@@ -4,14 +4,14 @@ The Buildah package provides a command line tool that can be used to
* create a working container, either from scratch or using an image as a
starting point
-* create an image, either from a working container or via the instructions in a
- Dockerfile
+* create an image, either from a working container or via the
+ instructions in a Dockerfile
* images can be built in either the OCI image format or the traditional
upstream docker image format
* mount a working container's root filesystem for manipulation
* unmount a working container's root filesystem
-* use the updated contents of a container's root filesystem as a filesystem
- layer to create a new image
+* use the updated contents of a container's root filesystem as a
+ filesystem layer to create a new image
* delete a working container or an image
* rename a local container
@@ -21,15 +21,16 @@ For examples, see:
non-root usage:
-plenty of kernel recent kernel's support the user-namespace sub uid/gid
-mapping. Only recent versions of shadow-utils will append a new mapping for
-users when they are created. You may have to add a mapping for your user like
-so:
+plenty of kernel recent kernel's support the user-namespace sub
+uid/gid mapping. Only recent versions of shadow-utils will append a
+new mapping for users when they are created. You may have to add a
+mapping for your user like so:
```shell
echo "$YOURUSER:100000:65536" > /etc/subuid
echo "$YOURGROUP:100000:65536" > /etc/subgid
```
-if you have more than one non-root user to add a mapping for, then their start
-number (like `100000` above) would begin after 100000+65536.
+if you have more than one non-root user to add a mapping for,
+then their start number (like `100000` above) would begin after
+100000+65536.