大网数据广告活动
服务器运维问答

Why do some host volumes in Docker containers give the error "too many levels of symbolic links"?

· 52CE 我爱测

I'm running docker with a host directory mounted: $ docker run -v /usr/groups/thing -ti imagename /bin/bash Files in /usr/groups/thing/foo are accessible: # ls /usr/groups/thing/foo a b c But files in /usr/groups/thing/bar are no…

问题原文

原帖链接 · Peter Westlake · CC BY-SA 3.0

I'm running docker with a host directory mounted:

$ docker run -v /usr/groups/thing -ti imagename /bin/bash

Files in /usr/groups/thing/foo are accessible:

# ls /usr/groups/thing/foo
a b c

But files in /usr/groups/thing/bar are not:

# ls /usr/groups/thing/bar
ls: cannot open directory /usr/groups/thing/bar: Too many levels of symbolic links

This is on Debian, and /usr/groups/thing is an automounted NFS volume.

已采纳解答

原帖链接 · Peter Westlake · CC BY-SA 3.0

This is caused by directories not being automounted when the container is run. I had thought that /usr/groups/thing was the automount point, but evidently the sub-directories are auto-mounted individually. The solution is to make sure each one is mounted before entering the container:

$ (cd /usr/groups/thing/foo; cd /usr/groups/thing/bar)
$ docker run -v /usr/groups/thing -ti imagename /bin/bash
# ls /usr/groups/thing/bar
d e f

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2014-10-30)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。