Skip to content
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

Use -v to map directories into the container, and use df-h to view disk mounts,show wrong infomation #45879

Closed
xuegege5290 opened this issue Jul 4, 2023 · 4 comments
Labels
area/volumes kind/bug Bugs are bugs. The cause may or may not be known at triage time so debugging may be needed. status/0-triage version/20.10

Comments

@xuegege5290
Copy link

xuegege5290 commented Jul 4, 2023

Description

When i use -v to map directories into the container, and use df-h to view disk mounts,show wrong infomation

$ docker run -itd --name t8 -v ~/docker:/home/sx/: -v ~/go:/home/go/ busybox:latest /bin/sh
d0fed1a003ef1dc12bd57d39772aa5869087b809259128bcf55851ef4ca0c70a

$ docker exec -it t8 /bin/sh                                                               
/ # 
/ # df -h /home/sx
Filesystem                Size      Used Available Use% Mounted on
/dev/mapper/data-home
                        290.4G    217.2G     58.4G  79% /home/sx
/ # df -h /home/go
Filesystem                Size      Used Available Use% Mounted on
/dev/mapper/data-home
                        290.4G    217.2G     58.4G  79% /home/sx

When i container ,use the df -h /home/go,but it show the wrong infomation!

But when i use the another images ,such as centos:8,it show the right mount infomation...

$ docker run -itd --name t8 -v ~/docker:/home/sx/: -v ~/go:/home/go/ centos:8 /bin/sh      
0ee1433ab9cd908648af6929b295165c8dd934e2bfd3db03c4c4ddb9dcdfa7cb

$ docker exec -it t8 /bin/sh                                                         
sh-4.4# df -h /home/sx
Filesystem             Size  Used Avail Use% Mounted on
/dev/mapper/data-home  291G  218G   59G  79% /home/sx
sh-4.4# df -h /home/go
Filesystem             Size  Used Avail Use% Mounted on
/dev/mapper/data-home  291G  218G   59G  79% /home/go

Reproduce

$ docker run -itd --name t8 -v ~/docker:/home/sx/: -v ~/go:/home/go/ busybox:latest /bin/sh
d0fed1a003ef1dc12bd57d39772aa5869087b809259128bcf55851ef4ca0c70a
$ docker exec -it t8 /bin/sh                                                               
/ # 
/ # df -h /home/sx
Filesystem                Size      Used Available Use% Mounted on
/dev/mapper/data-home
                        290.4G    217.2G     58.4G  79% /home/sx
/ # df -h /home/go
Filesystem                Size      Used Available Use% Mounted on
/dev/mapper/data-home
                        290.4G    217.2G     58.4G  79% /home/sx

Expected behavior

it should be like this :
1.

$ docker run -itd --name t8 -v ~/docker:/home/sx/: -v ~/go:/home/go/ centos:8 /bin/sh      
0ee1433ab9cd908648af6929b295165c8dd934e2bfd3db03c4c4ddb9dcdfa7cb
$ docker exec -it t8 /bin/sh                                                         
sh-4.4# df -h /home/sx
Filesystem             Size  Used Avail Use% Mounted on
/dev/mapper/data-home  291G  218G   59G  79% /home/sx
sh-4.4# df -h /home/go
Filesystem             Size  Used Avail Use% Mounted on
/dev/mapper/data-home  291G  218G   59G  79% /home/go

docker version

$ docker version            
Client: Docker Engine - Community
 Version:           20.10.17
 API version:       1.41
 Go version:        go1.17.11
 Git commit:        100c701
 Built:             Mon Jun  6 23:03:11 2022
 OS/Arch:           linux/amd64
 Context:           default
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          20.10.17
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.17.11
  Git commit:       a89b842
  Built:            Mon Jun  6 23:01:29 2022
  OS/Arch:          linux/amd64
  Experimental:     true
 containerd:
  Version:          1.5.9
  GitCommit:        3326bf27cc876c94597d8ede2b9a820e4e9ccff6
 runc:
  Version:          1.0.3
  GitCommit:        v1.0.0-rc93-500-gf46b6ba
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

docker info

$ docker info      
Client:
 Context:    default
 Debug Mode: false
 Plugins:
  app: Docker App (Docker Inc., v0.9.1-beta3)
  buildx: Docker Buildx (Docker Inc., v0.8.2-docker)
  compose: Docker Compose (Docker Inc., v2.6.0)

Server:
 Containers: 1
  Running: 1
  Paused: 0
  Stopped: 0
 Images: 40
 Server Version: 20.10.17
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 1
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 3326bf27cc876c94597d8ede2b9a820e4e9ccff6
 runc version: v1.0.0-rc93-500-gf46b6ba
 init version: de40ad0
 Security Options:
  seccomp
   Profile: default
 Kernel Version: 4.19.112-2.el8.x86_64

Additional Info

No response

@xuegege5290 xuegege5290 added kind/bug Bugs are bugs. The cause may or may not be known at triage time so debugging may be needed. status/0-triage labels Jul 4, 2023
@xuegege5290
Copy link
Author

@thaJeztah

@thaJeztah
Copy link
Member

Looks like this may be a bug in busybox?

@xuegege5290
Copy link
Author

Thanks for your quick replay!yes, i already verify it is busybox problem.In busybox image, it seems like the df binary has some problem.

@thaJeztah
Copy link
Member

closing in favour of mirror/busybox#71, but happy to reopen if it turns out there's things to address on our side.

@thaJeztah thaJeztah closed this as not planned Won't fix, can't repro, duplicate, stale Sep 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/volumes kind/bug Bugs are bugs. The cause may or may not be known at triage time so debugging may be needed. status/0-triage version/20.10
Projects
None yet
Development

No branches or pull requests

2 participants