New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ubuntu 16.04 kernel and Docker Swarm Mode #78

Closed
jesuscript opened this Issue Nov 9, 2016 · 14 comments

Comments

10 participants
@jesuscript
Copy link

jesuscript commented Nov 9, 2016

Hi,

I have been having problems with connectivity between different nodes in a Docker Swarm Mode cluster and it has been pointed out to me that the problem lies in my kernel missing IPVS modules needed for load balancing (IPVS_NFCT and IPVS_RR). See this thread for more details: moby/moby#28168

The kernel currently used in 16.04 images is 4.5.7-std-3. Is there another kernel that you could recommend which would have the required kernel configs and also work well on scaleway servers? Alternatively, I'm happy to follow any other recommendation for setting up a Docker Swarm cluster. Thanks!

@QuentinPerez

This comment has been minimized.

Copy link
Contributor

QuentinPerez commented Nov 9, 2016

Hi @jesuscript,

You must use the docker bootscript e.g 4.8.3 docker.
To use a different bootscript you can follow these instructions

@jesuscript

This comment has been minimized.

Copy link
Author

jesuscript commented Nov 9, 2016

cool, thanks! oddly, the instructions only talk about how to change a server's bootscript, but not how to select one before it's created. Do you know if it's even possible?

@QuentinPerez

This comment has been minimized.

Copy link
Contributor

QuentinPerez commented Nov 9, 2016

Yes you can, but only with the CLI scw run --bootscript=docker xenial

@jesuscript

This comment has been minimized.

Copy link
Author

jesuscript commented Nov 9, 2016

ahha! brilliant, thanks so much! Just one more thing: where is the best place to find the list of available bootscripts?

@QuentinPerez

This comment has been minimized.

Copy link
Contributor

QuentinPerez commented Nov 9, 2016

Currently you can only list the public bootscripts.

scw images -f type=bootscript
REPOSITORY                  TAG                 IMAGE ID            CREATED             REGION              ARCH
armv7l_4_8_3_std_1_latest   <bootscript>        84a15893            n/a                 []                  [arm]
x86_64_4_8_3_apparmor_1     <bootscript>        c2a7891b            n/a                 []                  [x86_64]
x86_64_4_8_3_std_1_latest   <bootscript>        4b9b80a5            n/a                 []                  [x86_64]
armv7l_4_4_26_std_1_stabl   <bootscript>        7d547f48            n/a                 []                  [arm]
x86_64_4_8_3_rancher_1      <bootscript>        d09eb9d6            n/a                 []                  [x86_64]
x86_64_4_8_3_fedora_1       <bootscript>        dafb7757            n/a                 []                  [x86_64]
x86_64_4_8_3_docker_1       <bootscript>        61648cb3            n/a                 []                  [x86_64]
x86_64_4_4_26_std_1_stabl   <bootscript>        20272fd0            n/a                 []                  [x86_64]
x86_64_4_8_3_debug_1        <bootscript>        1feffa10            n/a                 []                  [x86_64]
armv7l_4_8_3_docker_1       <bootscript>        e1ee48e3            n/a                 []                  [arm]
armv7l_4_8_3_apparmor_1     <bootscript>        5fef0f06            n/a                 []                  [arm]
armv7l_Rescue               <bootscript>        a5485ac0            n/a                 []                  [arm]
x86_64_rescue               <bootscript>        bf4cfb66            n/a                 []                  [x86_64]
armv7l_4_8_3_fedora_1       <bootscript>        bc2a2c2f            n/a                 []                  [arm]
@jesuscript

This comment has been minimized.

Copy link
Author

jesuscript commented Nov 9, 2016

awesome! I think that's all I need, thanks again

@jesuscript jesuscript closed this Nov 9, 2016

@zekiunal

This comment has been minimized.

Copy link

zekiunal commented Apr 27, 2017

Hi;

I am trying to run Docker Swarm Mode on Ubuntu Xenial (16.04 latest).

I am changing bootscript to x86_64 4.10.8 docker #1 and reboot then.

this is docker installation script :

sudo apt-get update -y
sudo apt-get install -y apt-transport-https ca-certificates curl software-properties-common nfs-common
curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -
sudo apt-key fingerprint 0EBFCD88
sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable"
sudo apt-get update
sudo apt-get install -y docker-ce
sudo systemctl enable docker
PRIVATE_IP=$(/sbin/ifconfig eth0 | grep Mask | awk '{print $2}'| cut -f2 -d:);
sudo docker swarm init --advertise-addr ${PRIVATE_IP}
sudo docker service rm nginx
sudo docker service create --name nginx --publish 80:80 nginx

But nginx cannot reachable via browser.

What's going on ? I could not move forward.

@VERGiL1202

This comment has been minimized.

Copy link

VERGiL1202 commented May 15, 2017

I am facing the same problem with the x86_64 4.10.8 docker #1 bootscript.
Scaleway support just says "we do not make assistance on docker configuration".
Well, it's related to your custom kernel Scaleway! Guess I have to switch my cloud provider if there is no solution here.

@mbenedettini

This comment has been minimized.

Copy link

mbenedettini commented Jun 4, 2017

Rancher bootscripts seem to include it. I'm currently using x86_64 4.10.8 rancher #1 and ports are being exposed just fine.

@insertjokehere

This comment has been minimized.

Copy link

insertjokehere commented Aug 27, 2017

This is still an issue - the latest docker bootscripts are missing IP_VS_NFCT which breaks swarm, and the x86_64 4.10.8 rancher #1 bootscript mentioned previously doesn't seem to exist any more

@tbillon

This comment has been minimized.

Copy link

tbillon commented Aug 28, 2017

We've merged the different configurations into the mainline kernel. It should contain everything you need for docker.

@neolectron

This comment has been minimized.

Copy link

neolectron commented Sep 8, 2017

I still have this issue with your debian9 image.

@painslie

This comment has been minimized.

Copy link

painslie commented Oct 2, 2017

@vadmeste I changed my Scaleway startup script to the latest mainline and it's working!!!

Thanks for all your help.

@lvnilesh

This comment has been minimized.

Copy link

lvnilesh commented Oct 31, 2017

I just built a Docker swarm using Debian Stretch and x86_64 mainline 4.13 and I can not get swarm nodes to communicate with each other.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment