LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 10-11-2018, 12:38 AM   #1
Sylvester Ink
Member
 
Registered: Jun 2010
Distribution: Slackware
Posts: 98

Rep: Reputation: 35
Building Docker on Slackware 14.2


I'm trying to build Docker on Slackware 14.2, using the slackbuild for version 18.03.1. The build fails with the message:
Code:
# WARNING! I don't seem to be running in the Docker container.
# The result of this command might be an incorrect build, and will not be
#   officially supported.
#
# Try this instead: make all
# 
# WARNING! I don't seem to be running in the Docker container.
# The result of this command might be an incorrect build, and will not be
#   officially supported.
#
# Try this instead: make all
#
I am running this on a Linode VM, and I haven't had a chance to test it on my home machine yet, but I don't think it's specific to the VM.
Could this be an issue with my setup, or is it something I should notify the maintainer about?
 
Old 10-11-2018, 02:00 AM   #2
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 3,838

Rep: Reputation: 1113Reputation: 1113Reputation: 1113Reputation: 1113Reputation: 1113Reputation: 1113Reputation: 1113Reputation: 1113Reputation: 1113
I had the same warning, but still it works at the end
 
1 members found this post helpful.
Old 10-11-2018, 01:03 PM   #3
Sylvester Ink
Member
 
Registered: Jun 2010
Distribution: Slackware
Posts: 98

Original Poster
Rep: Reputation: 35
I tried again, this time manually running the slackbuild (instead of sbopkg), and got this result:
Code:
# The result of this command might be an incorrect build, and will not be                                              
# officially supported.                                                                                                
#                                                                                                                      
# Try this instead: make all                                                                                           
#                                                                                                                      
                                                                                                                       
Removing bundles/                                                                                                      
                                                                                                                       
---> Making bundle: dynbinary (in bundles/dynbinary)                                                                   
Building: bundles/dynbinary-daemon/dockerd-18.03.1-ce                                                                  
/usr/lib64/go1.11/go/pkg/tool/linux_amd64/link: signal: killed
(It's the same as before, but I neglected to include the final few lines.)
It seems that I'm running out of memory when building it. I guess I'll have to figure out an alternative method for getting it installed.
 
Old 10-11-2018, 07:18 PM   #4
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 3,838

Rep: Reputation: 1113Reputation: 1113Reputation: 1113Reputation: 1113Reputation: 1113Reputation: 1113Reputation: 1113Reputation: 1113Reputation: 1113
did you use "su -" instead of just "su" ?
 
1 members found this post helpful.
Old 10-11-2018, 07:54 PM   #5
Sylvester Ink
Member
 
Registered: Jun 2010
Distribution: Slackware
Posts: 98

Original Poster
Rep: Reputation: 35
Quote:
Originally Posted by willysr View Post
did you use "su -" instead of just "su" ?
Yes, I did. It's definitely out of memory, as I get an OOM error in dmesg log. I'm trying to build on a server with only 1gb of RAM, which is probably not enough. And I suspect that if I did get the package built (perhaps on my own machine), running Docker will probably eat up that memory fairly quickly. Might be better off not using it for now.
 
Old 10-11-2018, 07:59 PM   #6
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 5,374

Rep: Reputation: 3141Reputation: 3141Reputation: 3141Reputation: 3141Reputation: 3141Reputation: 3141Reputation: 3141Reputation: 3141Reputation: 3141Reputation: 3141Reputation: 3141
If you're limited on RAM, have a look at a swap file. This would allow you to create a file on your computer in whatever size you deem necessary to allow swap usage. Once you are done with the build, you're free to delete the file or just turn the swap off (leaving the file there for any future usage). I use these occasionally when my RAM and swap partition are getting full to temporarily increase my swap size.
 
1 members found this post helpful.
Old 10-11-2018, 10:48 PM   #7
zakame
Member
 
Registered: Apr 2012
Distribution: Debian, Ubuntu, Slackware
Posts: 250

Rep: Reputation: 152Reputation: 152
Probably unrelated if you want to build from source, but I've made a SlackBuild for getting pre-built Docker CE from download.docker.com.
 
2 members found this post helpful.
Old 10-12-2018, 01:14 PM   #8
mralk3
Senior Member
 
Registered: May 2015
Location: Utah, USA
Distribution: Slackware 14.2 || Slackware-current && CentOS
Posts: 1,246

Rep: Reputation: 618Reputation: 618Reputation: 618Reputation: 618Reputation: 618Reputation: 618
Linode provides solid state drives for all linodes, so a swap file should be an acceptable option.
 
Old 10-12-2018, 04:09 PM   #9
Sylvester Ink
Member
 
Registered: Jun 2010
Distribution: Slackware
Posts: 98

Original Poster
Rep: Reputation: 35
Quote:
Originally Posted by bassmadrigal View Post
If you're limited on RAM, have a look at a swap file. This would allow you to create a file on your computer in whatever size you deem necessary to allow swap usage. Once you are done with the build, you're free to delete the file or just turn the swap off (leaving the file there for any future usage). I use these occasionally when my RAM and swap partition are getting full to temporarily increase my swap size.
This method worked perfectly!
Also zakame's SlackBuild should be great for those who may prefer the pre-built binary.
 
Old 10-13-2018, 01:07 AM   #10
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 4,423

Rep: Reputation: 2349Reputation: 2349Reputation: 2349Reputation: 2349Reputation: 2349Reputation: 2349Reputation: 2349Reputation: 2349Reputation: 2349Reputation: 2349Reputation: 2349
FYI, something similar is described also in SlackBuilds.org's FAQ

https://slackbuilds.org/faq/#build
 
1 members found this post helpful.
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Building Docker on 14.2 linuxbawks Linux - Containers 2 08-13-2018 02:18 PM
[SOLVED] Docker 1.13.1 building problem on Slackware 14.2 horizn Slackware 6 03-25-2017 10:29 AM
LXer: Docker Part 4: building and publishing custom docker images LXer Syndicated Linux News 0 04-08-2016 01:30 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 05:54 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration