SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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?
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.
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.
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.
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
