Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
GitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Coreos 1520.6.0 CIFS mount fails #2204
After upgraded coreos version (automatically updated), mounting a samba share with mount.cifs fails.
I read somewhere it might be related to not having md5 kernel module loaded, but I am not really sure.
The mounting was working for months in the same way.
Container Linux Version
The version is 1520.6.0 , from stable channel
CoreOs is running in VirtualBox. The same behavior happened both using Vbox in Windows and in Linux.
mount.cifs should be able to mount a shared directory, when the correct address, user and options are passed to it.
After prompting for the user's password, the mount fails with
There are no many references of similar bugs in the past, but I found a similar one in rear/rear#149 and here https://www.linuxquestions.org/questions/linux-kernel-70/cannot-load-md5-ko-module-911608/ . They are both related to completely different systems, but maybe the root is similar.
Got the same problem here.
To be more precise, it is no longer possible to mount SMB 3.0 shares in CoreOS Container Linux. However mounting the CIFS shares using protocol version 2.1 or lower is still working (i.e. using
It seems to appear since CoreOS Container Linux 1520.5.0 (is it related to the migration to kernel 4.13?).
Reading the source code of CIFS support in the kernel shows that SMB3 require cmac(aes) which is provided by CMAC crypto module . This kernel module (
Thanks for the details, it was very helpful to get which module is missing.
I can also confirm that overriding the version to 2.1 the mount works, despite we were using 3.02 to solve some specific issue with node module installing.
I also supposed it was related to kernel change from version 1520.5.0 , but I can't confirm, since I didn't have the chance to test this specific version.