[SOLVED] building docker from SBo fails

nass · 07-28-2021, 07:29 PM

Hi all,
I see that ponce here has managed to build docker just after installing google-go-lang using sbopkg and the 14.2 slackbuilds repo.

Well I have issues during `sbopkg -i docker`.
After extraction of the sources is complete

Quote:

[... extraction preceeded ... ]
moby-20.10.2/volume/testutils/testutils.go
moby-20.10.2/volume/volume.go

Removing bundles/

---> Making bundle: dynbinary (in bundles/dynbinary)
Building: bundles/dynbinary-daemon/dockerd-20.10.2
GOOS="" GOARCH="" GOARM=""
no required module provides package github.com/docker/docker/cmd/dockerd: go.mod file not found in current directory or any parent directory; see 'go help modules'

Do you also get this error?

I tried to temporarily switch to Ponce's SBo-git/current repo just to see if it will work. Using ponce's slackbuilds the build succeeded but rc.docker would not start the dockerd daemon. running the daemon alone I see the following error :

Quote:

failed to start daemon: error initializing graphdriver: devicemapper: Error running deviceCreate (CreatePool) dm_task_run failed

which led me to the link above.

SO have you been able to install docker in slackware64 14.2 ?

Thank you

willysr · 07-28-2021, 08:47 PM

i think you mixed between 14.2 and Ponce's current repo.
If you want to build for 14.2, stick with the one in SBo and always, run "su -" before running the build process for all packages.

nass · 07-30-2021, 01:16 AM

hi there,
I only mixed them intentionally. It was only after the 14.2 repo failed to successfully build docker that I tried ponce's repo.
Sticking to 14.2 though it fails and I wonder if anyone has had the same issue.

To be precise: it seems as if there is a step missing in the slackbuild or that somehow the build process has changed since the slackbuild was implemented. And I would like to verify if currently using the 14.2 repo somebody (other than me) wanting to install docker would succeed.

ponce · 07-30-2021, 01:24 AM

I think it fails because of the upgrade of google-go-lang to 1.16.3: some components of the docker build queue need an additional line to satisfy the newer google-go-lang but this has been added only to SBo's master branch on git, not on the 14.2 repository because submission closed before we found out about this.

for example docker-proxy.SlackBuild has to be amended like this

Code:

@@ -60,6 +60,7 @@ find -L . \
 mkdir build
 mv vendor build/src
 
+GO111MODULE=auto \
 GOPATH=$TMP/$SRCNAM-$GITHASH/build \
 go build -o $PKG/usr/bin/docker-proxy ./cmd/proxy

the alternative is to revert google-go-lang to version 1.14.14.

nass · 07-30-2021, 04:52 AM

Hm in that case and since I already successfully slackbuilt the rest of the dependencies from Ponce's repo and that failed to start the dockerd successfully, it makes sense to go the other way and downgrade google-go-lang.

Is is possible to do that using sbopkg?
I mean I would normally need to

copy google-go-lang.tar.gz ad extract under the local repo in /var/lib/sbopkg/local/

Code:

cp /var/lib/sbopkg/SBo/14.2/development/google-go-lang/google-go-lang.tar.gz /var/lib/sbopkg/local/development/google-go-lang/google-go-lang
tar xzvf /var/lib/sbopkg/local/development/google-go-lang/google-go-lang/google-go-lang.tar.gz

update the .Slackbuild to point to version 1.14.14, and the .info file with where to get the latest file from .
sbopkg -V local/local
then I try to browse for the google-go-land, but the "readme" and "info" commands cannot open the respective files, and the "install" command points to 1.16.3 version, possibly because there exist the previously created pkg at /root/SBoTGZ/google-go-lang-1.16.3-x86_64-1_SBo.tgz as seen in the attached image Screenshot_2021-07-30_11-37-14.png .
if I remove the .tgz I still cannot start the build. The error is shown in Screenshot_2021-07-30_11-51-42.png

So am I using the sbopkg wrongly here ?
Is my only option to perform the slackbuild completely independent of sbopkg?

nass · 08-02-2021, 08:27 AM

OK to close this thread properly,
I did manage to build containerd, docker-proxy, docker and docker-cli locally with or without sbopkg (had to delete the .tgz from the $OUTPUT dir).
I had to manually add the GO111MODULE=auto in the aforementioned slackbuilds, as mentioned by Ponce and explained here.

In the end I still had issues with running docker that included:
- failing to start because of devicemapper errors (this).
- failing to start because of cgroup errors
- starting but "docker info" would hang there
- starting but "docker info" would report it could not connect to the unix socket.

I somehow ended up finding this check-config.sh script which checks for kernel support for docker. I recompiled the kernel with all the necessary options and viola, it works!

EDIT:
Ah this is where I found out about it : https://www.linuxquestions.org/quest...ml#post6213662