Installing Podman Debian 9 lxhaddcs XY

Introduction

• skipped, due to upgrade of debian on some lxhaddcsxy to debian 10

Installation

Packages

sudo apt-get install \ 
  btrfs-tools \ 
  git \ 
  golang-go \ 
  go-md2man \ 
  iptables \ 
  libassuan-dev \ 
  libbtrfs-dev \ 
  libc6-dev \ 
  libdevmapper-dev \ 
  libglib2.0-dev \ 
  libgpgme-dev \ 
  libgpg-error-dev \ 
  libprotobuf-dev \ 
  libprotobuf-c0-dev \ 
  libseccomp-dev \ 
  libselinux1-dev \ 
  libsystemd-dev \ 
  pkg-config \ 
  runc \ 
  uidmap

for item in $(echo "\ 
 install \ 
  btrfs-tools \ 
  git \ 
  golang-go \ 
  go-md2man \ 
  iptables \ 
  libassuan-dev \ 
  libbtrfs-dev \ 
  libc6-dev \ 
  libdevmapper-dev \ 
  libglib2.0-dev \ 
  libgpgme-dev \ 
  libgpg-error-dev \ 
  libprotobuf-dev \ 
  libprotobuf-c0-dev \ 
  libseccomp-dev \ 
  libselinux1-dev \ 
  libsystemd-dev \ 
  pkg-config \ 
  runc \ 
  uidmap" | xargs):
  do 
   sudo apt-get $item || break;
done

Building missing dependencsies

golang

$> go version
go version go1.7.4 linux/amd64

export GOPATH=~/go
git clone https://go.googlesource.com/go $GOPATH
cd $GOPATH
cd src
./all.bash
export PATH=$GOPATH/bin:$PATH

Get Source Code

export GOPATH=~/go && mkdir -p $GOPATH
 

git clone https://github.com/containers/podman/ $GOPATH/src/github.com/containers/podman

cd $GOPATH/src/github.com/containers/podman

make BUILDTAGS="selinux seccomp"

sudo make install PREFIX=/usr 

sudo make install PREFIX=/usr
go build -mod=vendor  -gcflags 'all=-trimpath=' -asmflags 'all=-trimpath=' -ldflags '-X github.com/containers/podman/v2/libpod/define.gitCommit=453333a35cc791e9031e5d24e0ac5e76a2b2aa75 -X github.com/containers/podman/v2/libpod/define.buildInfo=1601423368 -X github.com/containers/podman/v2/libpod/config._installPrefix=/usr -X github.com/containers/podman/v2/libpod/config._etcDir=/etc ' -tags "   selinux systemd exclude_graphdriver_devicemapper seccomp" -o bin/podman ./cmd/podman
flag provided but not defined: -mod
usage: build [-o output] [-i] [build flags] [packages]

Build compiles the packages named by the import paths,
along with their dependencies, but it does not install the results.

If the arguments to build are a list of .go files, build treats
them as a list of source files specifying a single package.

When compiling a single main package, build writes
the resulting executable to an output file named after
the first source file ('go build ed.go rx.go' writes 'ed' or 'ed.exe')
or the source code directory ('go build unix/sam' writes 'sam' or 'sam.exe').
The '.exe' suffix is added when writing a Windows executable.

When compiling multiple packages or a single non-main package,
build compiles the packages but discards the resulting object,
serving only as a check that the packages can be built.
.....