bottlerocket-os / bottlerocket-os/bottlerocket
samba mount error (but same command worked on self-managed EKS nodes of amazonlinux2)
- Dominant language
- Rust
- Stars
- 9.7k
- Forks
- 586
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 12
Description
**Image I'm using:**
OS Image: Bottlerocket OS 1.14.2 (aws-k8s-1.25)
Container Runtime Version: containerd://1.6.20+bottlerocket
particular container is based on python:3.10.11-slim with apt install -y cifs-utils
**What I expected to happen:**
mount command to onprem windows share would succeed
**What actually happened:**
bash exit code 32
```
mount.cifs kernel mount options: ip=redactedIP,unc=\\redacted\Shared,seal,vers=3.0,user=redacted,domain=NTADMIN,prefixpath=redacted\redacted,pass=********
mount error(4): Interrupted system call
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
```
dmesg shows:
```
[72908.566487] Key type dns_resolver registered
[72908.658049] Key type cifs.spnego registered
[72908.658056] Key type cifs.idmap registered
[72908.658944] CIFS: Attempting to mount \\redacted\Shared
[72908.864573] CIFS: VFS: cifs_mount failed w/return code = -4
```
Note that exact same steps work on EKS 1.25 self-managed nodes based on amazonlinux2 with same python image for containers as above. I've also confirmed /etc/resolv.conf have same values and that port is reachable (timeout 7 bash -c ">/dev/tcp/redact/445" &>/dev/null && echo "Online" || echo "Offline")
Also files can be accessed from this jar: https://github.com/hierynomus/smbj
**How to reproduce the problem:**
```
mkdir -p /mnt/my_mount_dir
echo -e "username=redact\npassword=redact" > p.ini
mount -vvv -t cifs -o "domain=NTADMIN,credentials=/p.ini,seal,vers=3.0" '\\redacted\Shared\redacted\redacted' /mnt/my_mount_dir
echo $?
dmesg
```
Contributor guide
Research direction
Start with the reported mount.cifs reproduction using cifs-utils, then compare the Bottlerocket 1.14.2 dmesg output with the working Amazon Linux 2 EKS nodes. Check the kernel CIFS mount path and the documented SMB options, including vers=3.0 and seal. Done means identifying the cause of return code -4 and recording a verified fix or limitation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- networking, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100