diff options
Diffstat (limited to 'install.md')
| -rw-r--r-- | install.md | 62 |
1 files changed, 44 insertions, 18 deletions
diff --git a/install.md b/install.md index 94de2ea74..49a67f984 100644 --- a/install.md +++ b/install.md @@ -2,7 +2,7 @@ ## Installing packaged versions of Podman -#### [Arch Linux](https://www.archlinux.org) +#### [Arch Linux](https://www.archlinux.org) & [Manjaro Linux](https://manjaro.org) ```bash sudo pacman -S podman @@ -138,6 +138,32 @@ sudo apt-get install \ uidmap ``` +On Manjaro (and maybe other Linux distributions): + +Make sure that the Linux kernel supports user namespaces: + +``` +> zgrep CONFIG_USER_NS /proc/config.gz +CONFIG_USER_NS=y + +``` + +If not, please update the kernel. +For Manjaro Linux the instructions can be found here: +https://wiki.manjaro.org/index.php/Manjaro_Kernels + +After that enable user namespaces: + +``` +sudo sysctl kernel.unprivileged_userns_clone=1 +``` + +To enable the user namespaces permanently: + +``` +echo 'kernel.unprivileged_userns_clone=1' > /etc/sysctl.d/userns.conf +``` + ### Building missing dependencies If any dependencies cannot be installed or are not sufficiently current, they have to be built from source. @@ -193,7 +219,7 @@ To build from source, use the following: git clone https://github.com/containers/conmon cd conmon make -sudo install -D -m 755 bin/conmon /usr/libexec/podman/conmon +sudo make podman ``` #### runc @@ -226,7 +252,7 @@ A proper description of setting up CNI networking is given in the [`cni` README] Using the CNI plugins from above, a more basic network config is achieved with: ```bash -mkdir -p /etc/cni/net.d +sudo mkdir -p /etc/cni/net.d curl -qsSL https://raw.githubusercontent.com/containers/libpod/master/cni/87-podman-bridge.conflist | sudo tee /etc/cni/net.d/99-loopback.conf ``` @@ -273,7 +299,7 @@ First, ensure that the go version that is found first on the $PATH (in case you git clone https://github.com/containers/libpod/ $GOPATH/src/github.com/containers/libpod cd $GOPATH/src/github.com/containers/libpod make BUILDTAGS="selinux seccomp" -sudo make install PREFIX= +sudo make install PREFIX=/usr ``` #### Build Tags @@ -292,23 +318,23 @@ To add build tags to the make option the `BUILDTAGS` variable must be set, for e make BUILDTAGS='seccomp apparmor' ``` -| Build Tag | Feature | Dependency | -|-----------|------------------------------------|-------------| -| seccomp | syscall filtering | libseccomp | -| selinux | selinux process and mount labeling | libselinux | -| apparmor | apparmor profile support | libapparmor | +| Build Tag | Feature | Dependency | +|----------------------------------|------------------------------------|----------------------| +| apparmor | apparmor support | libapparmor | +| exclude_graphdriver_btrfs | exclude btrfs | libbtrfs | +| exclude_graphdriver_devicemapper | exclude device-mapper | libdm | +| libdm_no_deferred_remove | exclude deferred removal in libdm | libdm | +| ostree | ostree support (requires selinux) | ostree-1, libselinux | +| containers_image_ostree_stub | exclude ostree | | +| seccomp | syscall filtering | libseccomp | +| selinux | selinux process and mount labeling | | +| systemd | journald logging | libsystemd | -### Vendoring - Dependency Management - -This project is using [vndr](https://github.com/LK4D4/vndr) for managing dependencies, which is a tedious and error-prone task. Doing it manually is likely to cause inconsistencies between the `./vendor` directory (i.e., the downloaded dependencies), the source code that imports those dependencies and the `vendor.conf` configuration file that describes which packages in which version (e.g., a release or git commit) are a dependency. - -To ease updating dependencies, we provide the `make vendor` target, which fetches all dependencies mentioned in `vendor.conf`. `make vendor` whitelists certain packages to prevent the `vndr` tool from removing packages that the test suite (see `./test`) imports. +Note that Podman does not officially support device-mapper. Thus, the `exclude_graphdriver_devicemapper` tag is mandatory. -The CI of this project makes sure that each pull request leaves a clean vendor state behind by first running the aforementioned `make vendor` followed by running `./hack/tree_status.sh` which checks if any file in the git tree has changed. - -##### Vendor Troubleshooting +### Vendoring - Dependency Management -If the CI is complaining about a pull request leaving behind an unclean state, it is very likely right about it. Make sure to run `make vendor` and add all the changes to the commit. Also make sure that your local git tree does not include files not under version control that may reference other go packages. If some dependencies are removed but they should not, for instance, because the CI is needing them, then whitelist those dependencies in the `make vendor` target of the Makefile. Whitelisting a package will instruct `vndr` to not remove if during its cleanup phase. +This project is using [go modules](https://github.com/golang/go/wiki/Modules) for dependency management. If the CI is complaining about a pull request leaving behind an unclean state, it is very likely right about it. After changing dependencies, make sure to run `make vendor` to synchronize the code with the go module and repopulate the `./vendor` directory. ## Configuration files |