Existing specific version number requirement is misleading; discussion
in https://github.com/containers/podman/issues/10100. Consensus there
and in #3295 is to avoid specific version numbers.
Signed-off-by: Steve Traugott <stevegt@t7a.org>
This commit removes installation steps for older distros:
1. Amazon Linux 2
2. CentOS 7
3. Debian 10
4. Raspbian 10
5. Raspberry Pi OS armhf
We're no longer building new packages for these distros and the
installation steps for older packages are no longer guaranteed to work.
So, these are best removed from the official docs.
Related blog post (also applies to buildah):
https://podman.io/blogs/2021/03/02/podman-support-for-older-distros.html
Signed-off-by: Lokesh Mandvekar <lsm5@fedoraproject.org>
Add target: make all DEBUG=1.
Uses the -N -l go compiler options to disable compiler optimizations
and inlining. Using these build options allows you to subsequently
use source debugging tools like delve.
Signed-off-by: Bogdan Dobrelya <bdobreli@redhat.com>
Buildah is now present on debian testing and unstable so providing Kubic
repos for it can lead to conflicts. Better to mention only the official
repos to avoid confusing end users.
Related: https://github.com/containers/buildah/issues/2797
Also, provide installation steps for Ubuntu 20.10 and newer, and redirect
Raspberry Pi OS users to Debian installation steps to
avoid content duplication.
Signed-off-by: Lokesh Mandvekar <lsm5@fedoraproject.org>
The Buildah project is committed to inclusivity, a core value of open source. Historically, there have been technology terms that are problematic and divisive, and should be changed. We are currently taking time to audit our repository in order to eliminate such terminology, and replace it with more inclusive terms. We are starting where we can, with our own code, comments, and documentation. However, such terms may be used in dependencies, and must be used as-is in our repositories at the current moment for compatibility. Buildah will change these terms in our repo as soon as new and better terminology is available to us via our dependencies.
For more information: https://www.redhat.com/en/blog/making-open-source-more-inclusive-eradicating-problematic-language?sc_cid=701600000011gf0AAA
Signed-off-by: Ashley Cui <acui@redhat.com>
2160: Adjust Ubuntu install info to also work on Pop!_OS r=rhatdan a=leorochael
Tested on `Pop!_OS` 19.10
2162: include installation steps for CentOS7 and forks r=rhatdan a=lsm5
Signed-off-by: Lokesh Mandvekar <lsm5@fedoraproject.org>
need confirmation on amazon linux 2 from https://github.com/containers/buildah/issues/1921 but I'm guessing this will work if amazon linux 2 is rhel7 compatible.
/cc @apg036 and @cgeers
Co-authored-by: Leonardo Rochael Almeida <leorochael@gmail.com>
Co-authored-by: Lokesh Mandvekar <lsm5@fedoraproject.org>
Fixed a typo on markdown link for Podman, revised build instructions for correctness, reviewed & added consistent sudo usage for Debian and Ubuntu.
Signed-off-by: Daniel Calvo <vioseven@gmail.com>
After commit 92ce0bdf, golang dependency for compiling is 1.12 or
higher.
Signed-off-by: Lu Jingxiao <lujingxiao@huawei.com>
Closes: #2013
Approved by: rhatdan
Thanks to Dmitry Smirnov @onlyjob for suggesting this tool.
Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
Closes: #1985
Approved by: TomSweeneyRedHat
Certain versions of go have different vendoring capabilities.
We want to make sure that vendoring the the vendor checker are
running with the same version of golang. We do this by using
podman to run a container of the lates golang container image.
Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
Closes: #1949
Approved by: TomSweeneyRedHat
It is now possible to simplify entries in `mounts.conf` files if the
source and destination paths are equal, like this:
```
/my/very/long/path:/my/very/long/path
```
can be now written as:
```
/my/very/long/path
```
The documentation has been adapted as well as the testing.
Signed-off-by: Sascha Grunert <sgrunert@suse.com>
Closes: #1832
Approved by: TomSweeneyRedHat
Add steps on how to use your own fork to vendor in code using go mod
to the install instructions.
Signed-off-by: TomSweeneyRedHat <tsweeney@redhat.com>
Closes: #1781
Approved by: rhatdan
When building buildah outside of the `$GOPATH`, then we should stick to
the `-mod=vendor` approach. Other go versions than 1.11 will build on
the classic way, whereas other targets should not be affected at all.
The documentation has been updated as well.
Signed-off-by: Sascha Grunert <sgrunert@suse.com>
Closes: #1752
Approved by: rhatdan
Added instructions for how to use go mod to vendor
in the contributing.md file.
Also add a few links to the Buildah mailing list.
Signed-off-by: TomSweeneyRedHat <tsweeney@redhat.com>
Closes: #1703
Approved by: rhatdan
Add a section about how we do vendoring and to troubleshoot related
issues. Note that the text is a verbatim copy from libpod's
install.md.
Signed-off-by: Valentin Rothberg <rothberg@redhat.com>
Closes: #1354
Approved by: rhatdan
We need to simply describe how to install a packaged
version of buildah for each distribution, rather then
just describing how to build it.
Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
Closes: #1310
Approved by: TomSweeneyRedHat
Signed-off-by: TomSweeneyRedHat <tsweeney@redhat.com>
We've had a couple of comments that the required configuration
files are not as documented as they should be. Adding a note to
the install and troubleshooting guides to hopefully help.
Signed-off-by: TomSweeneyRedHat <tsweeney@redhat.com>
Closes: #1306
Approved by: rhatdan
The link to the container-registries.conf man page was a little off - this fixes it.
This patch was originaly submitted by Kris Nova <kris@nivenly.com>
I am signing it to get it merged.
Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
Closes: #1153
Approved by: rhatdan
Use CNI to configure networks for containers for which we create new
network namespaces.
Signed-off-by: Nalin Dahyabhai <nalin@redhat.com>
Closes: #700
Approved by: rhatdan