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.
and don't forget to logout from your root session and login again after having installed google-go-lang: it's required to build some of the dependencies as this way some files in /etc/profile.d will be sourced to use google's go compiler instead of gcc's one, it's explained in google-go-lang's README.
I too can confirm that it builds and runs fine on current as I tested just yesterday.
I have docker-compose 1.25.1 running on -current. It has a rather long list of dependencies (and dependencies of dependencies) so it's a bit of a chore, but it works fine once it's installed. At one point I was going to create a script to automate the installation of it but I got distracted.
This will pull d-c as a Docker image that can run as a container app a la Flatpak/AppImage; run it at least once, even with just ./docker-compose help.
docker-machine is a bit more trouble, though the release binaries themselves are relatively straightforward to install; its the machine-drivers that you'll need to further set up, which will depend on whether you want/need (e.g. whether you'd be using docker-machine-kvm for driving libvirt machines, or use an external cloud driver entirely.)
I'm actually taking a Udemy course on Docker & Kubernetes - so I'm hacking my way through getting the environment setup....I'm just not that savvy when it comes to figuring this stuff out on Slackware. On Centos it was easy peasy, but I want to stay with Slackware, so.....I'm doing it the hard way I guess : )
I'm actually taking a Udemy course on Docker & Kubernetes - so I'm hacking my way through getting the environment setup....I'm just not that savvy when it comes to figuring this stuff out on Slackware. On Centos it was easy peasy, but I want to stay with Slackware, so.....I'm doing it the hard way I guess : )
My advice: follow the course on a CentOS 7 host machine (5 minutes to install it, plus one 1 minute to install Docker) and once you're proficient with Docker, you can always come back and install/use it on a Slackware host along with Slackware container images.
BTW, is that Jason Cannon's course you're following ?
I actually did the course using Centos 7, and it's Bret Fishers course. I thought it would be fun to get it running on Slackware, because that's my flavor of Linux. I just bought Bret's course on Kubernetes this morning : )
It is fun, and easy enough, to run Docker + Kubernetes on Slackware. Minikube runs well enough once you've gotten docker-machine-driver-kvm2 set up to talk to libvirt (and you can reuse that driver for Swarm machines as well,) though if you're already have dockerd running, you can just run KinD or k3d to run k8s nodes in Docker without virtualization.
OTOH there really isn't anything Slackware specific for building Docker + Kubernetes tooling (as opposed to running, which might need some things like a new kernel and/or cgroups shims, depending on workload,) as many of these modern tools use Golang/Rust and often already release static binaries precisely to avoid portability concerns in the varying Linux distros.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.