[Slackbuilds-users] Update request Docker

Fri Jan 20 19:13:20 UTC 2017

Maykon,

Thanks for feedback, appreciated :)

1 - Yeah, I should have stated that information ( get the 64bits source .tar.gz from  )

2- Didn't needed that to build and install successfully 1.12.5, I will take a look because sounds a good thing to do :)

3 - Yes, I need to take some time to review that part .
Well I guess I made some sort of bruteforce to understand how this was used ...

4 - will test, I didn't realized about those errors

5 -  runc and containerd , yes ! I didn't remember about that, I needed to install those 2 packages as well
So it should be added as dependencies

Did you need to run docker with a generic linux kernel ( not the Huge one  ) ?
Did you also need to add the daemon.json file to make it work ( or pass option in rc.docker ) ?

Thanks and Regards ,
Nico

-----Original Message-----
From: Maykon Chagas [mailto:mchagas at member.fsf.org] 
Sent: Friday, January 20, 2017 1:21 PM
To: Nicolas Lodpp <slack at lodpp.net>; slackbuilds-users (slackbuilds-users at slackbuilds.org) <slackbuilds-users at slackbuilds.org>
Subject: Re: [Slackbuilds-users] Update request Docker

Hi Nico,

FYI, your package builds fine! But no with a lot of test. Here's a bit about my journey.

1. You need to download source from this URL:
https://github.com/docker/docker/tags

2. You need to change GITHASH var with the one related to your version.

3. After a lot of try with version 1.12.5, 1.12.6 and 1.13.0 the packages with version 1.12.6 builds and work it. I've noticed that the binary in /usr/bin/dockerd was a symlink do /usr/bin/dockerd-${VERSION} but this one, doesn't exist. I don't know why, and when this was created in the Slackbuild script. You just have some mv bundles and not ln commands

4. If you tried to build a package, you need to close your terminal, or open another tab, otherwise, you'll receive errors like these:

---> Making bundle: dynbinary (in bundles/1.12.6/dynbinary)
Building: bundles/1.12.6/dynbinary-client/docker-1.12.6
go build: when using gccgo toolchain, please pass linker flags using -gccgoflags, not -ldflags # github.com/docker/distribution/registry/api/errcode
vendor/src/github.com/docker/distribution/registry/api/errcode/register.go:74:24:
error: reference to undefined identifier 'http.StatusTooManyRequests'
   HTTPStatusCode: http.StatusTooManyRequests,
                        ^
# github.com/docker/docker/api/client/inspect
.gopath/src/github.com/docker/docker/api/client/inspect/inspector.go:115:26:
error: reference to undefined field or method 'Option'
  tmplMissingKey := i.tmpl.Option("missingkey=error")

Well, that's was some things that I've noticed during my tests.

runc and containerd are dependencies?

At least now I can user docker-compose, and I've already test and it works!

Thanks to everyone, and specially to Nico!

Kind regars.

Em 01/19/2017 11:02 PM, Nicolas Lodpp escreveu:
> Hi everybody,
> 
> I've checked my slackbuild and corrected it to fit the 1.13.0 docker version, it creates the package fine.
> As 1.12.5 is working fine for me, I didn't test the 1.13.0 ( at least 
> not at 1 am :) )
> 
> Please be kind, I'm new about slackbuilds and I guess my modification are not the smartest moves...
> 
> I put the slackbuild on github: 
> https://github.com/lodpp/Slackbuilds/tree/master/docker
> file modified are:
> - slackbuild itself
> - rc.docker
> - daemon.json was needed on my setup to pass some options ( note that 
> it could be done on the rc file to with the variable DOCKER_OPTS= )
> 
> Regards,
> Nico
> 
> -----Original Message-----
> From: Maykon Chagas [mailto:mchagas at riseup.net]
> Sent: Thursday, January 19, 2017 8:58 PM
> To: slackware stuff <slack at lodpp.net>
> Subject: Re: [Slackbuilds-users] Update request Docker
> 
> Hi Nico,
> 
> I've send an email to in responso on slackbuilds-users list.
> Could you share your slackbuild script to Docker?
> 
> Thanks!
> 
> Em 01/19/2017 04:09 PM, slackware stuff escreveu:
>> Hi Ryan, Maykon,
>>
>> I've made a modified version for docker 1.12 and compiles fine ( should be okay for  1.13 though )if you are interested.
>>
>> I've contacted Vincent Batts  about the need for update He responds 
>> couple a days ago that Assaf is taking charge for the docker ( and I 
>> didn't got time to look for assaf email on the ml archive / sb site )
>>
>> Best regards,
>>
>> Nico
>>
>>
>>
>> ________________________________________
>> De : SlackBuilds-users <slackbuilds-users-bounces at slackbuilds.org> de 
>> la part de Maykon Chagas <mchagas at member.fsf.org> Envoyé : jeudi 19 
>> janvier 2017 18:43 À : slackbuilds-users at slackbuilds.org Objet : Re:
>> [Slackbuilds-users] Update request Docker
>>
>> Hi Ryan,
>>
>> Your answers came directly to me.
>>
>> Ok, I'll do this!
>>
>> Thanks!
>>
>> Kind regars,
>>
>> Em 01/19/2017 03:22 PM, Ryan P.C. McQuen escreveu:
>>> On 1/19/17, Maykon Chagas <mchagas at riseup.net> wrote:
>>>> Hi Ryan,
>>>>
>>>> Sorry. No. That's the flow? Ask directly the mantainer?
>>>
>>>
>>> Usually it's better to ask the maintainer first, and then this list 
>>> if there is no prompt response from the maintainer. Not all 
>>> maintainers are subscribed to this list.
>>>
>> _______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>>
>> _______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>>