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

`/bin/bash -c pwd` does not work in extracted directory with Btrfs #2056

Closed
paulepanter opened this issue Oct 1, 2013 · 5 comments
Closed

`/bin/bash -c pwd` does not work in extracted directory with Btrfs #2056

paulepanter opened this issue Oct 1, 2013 · 5 comments

Comments

@paulepanter
Copy link

@paulepanter paulepanter commented Oct 1, 2013

Using a Btrfs partition for storing the containers, extracting an archive and running ./configure.

    # ./configure 
    pwd: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
    configure: error: working directory cannot be determined
    root@file:/tmp/file-5.08# pwd
    /tmp/file-5.08
    root@file:/tmp/file-5.08# /bin/bash -c pwd
    shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
    pwd: error retrieving current directory: getcwd: cannot access parent directories: No such file or director
    root@file:/tmp/file-5.08# ls
    ls: cannot open directory .: Stale NFS file handle

Here are the steps to reproduce this issue.

    root@file:/tmp# wget ftp://ftp.astron.com/pub/file/file-5.08.tar.gz
    --2013-10-01 12:44:59--  ftp://ftp.astron.com/pub/file/file-5.08.tar.gz
               => `file-5.08.tar.gz'
    Resolving ftp.astron.com (ftp.astron.com)... 208.77.212.98, 38.117.134.204
    Connecting to ftp.astron.com (ftp.astron.com)|208.77.212.98|:21... connected.
    Logging in as anonymous ... Logged in!
    ==> SYST ... done.    ==> PWD ... done.
    ==> TYPE I ... done.  ==> CWD (1) /pub/file ... done.
    ==> SIZE file-5.08.tar.gz ... 605337
    ==> PASV ... done.    ==> RETR file-5.08.tar.gz ... done.
    Length: 605337 (591K) (unauthoritative)

    100%[===================================================================================================================================================================================================================================================================================>] 605,337      545K/s   in 1.1s

    2013-10-01 12:45:02 (545 KB/s) - `file-5.08.tar.gz' saved [605337]

    root@file:/tmp# tar xf file-5.08.tar.gz
    root@file:/tmp# cd file-5.08
    root@file:/tmp/file-5.08# ./configure
    pwd: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
    configure: error: working directory cannot be determined

Using Ext4 works as expected.

    joe@Ubuntu-1204-precise-64-minimal:~$ more /etc/os-release
    NAME="Ubuntu"
    VERSION="12.04.3 LTS, Precise Pangolin"
    ID=ubuntu
    ID_LIKE=debian
    PRETTY_NAME="Ubuntu precise (12.04.3 LTS)"
    VERSION_ID="12.04"
    joe@Ubuntu-1204-precise-64-minimal:~$ dpkg -l lxc-docker
    Desired=Unknown/Install/Remove/Purge/Hold
    | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
    |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
    ||/ Name                                                                      Version                                                                   Description
    +++-=========================================================================-=========================================================================-==================================================================================================================================================================
    ii  lxc-docker                                                                0.6.3                                                                     lxc-docker is a Linux container runtime
    joe@Ubuntu-1204-precise-64-minimal:~$ uname -a
    Linux Ubuntu-1204-precise-64-minimal 3.8.0-31-generic #46~precise1-Ubuntu SMP Wed Sep 11 18:21:16 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
@unclejack
Copy link
Contributor

@unclejack unclejack commented Oct 2, 2013

This isn't going to be an issue in 0.7. AUFS is being dropped (temporarily) in favor of device mapper.

@crosbymichael
Copy link
Member

@crosbymichael crosbymichael commented Nov 27, 2013

@paulepanter Can you try this again with docker 0.7?

@paulepanter
Copy link
Author

@paulepanter paulepanter commented Nov 29, 2013

Sorry, we do use Ext4 instead of Btrfs now. So I cannot test. Unclejack was able to reproduce this though I think.

@unclejack
Copy link
Contributor

@unclejack unclejack commented Nov 30, 2013

@paulepanter is right, I can reproduce this issue using the steps he's provided.

@unclejack
Copy link
Contributor

@unclejack unclejack commented Feb 21, 2014

There's a native btrfs driver now. That one should be used instead of attempting to use AUFS on top of btrfs.

I'll close this issue now since we're not going to support AUFS on top of btrfs for now. Please feel free to comment.

@unclejack unclejack closed this Feb 21, 2014
mboersma added a commit to deis/deis that referenced this issue Apr 10, 2014
When using aufs in docker on coreos, obscure errors show up, such
as python's gevent not building for autoconf errors. Specifying
btrfs as the filesystem fixes it.
See moby/moby#2056
mboersma added a commit to deis/deis that referenced this issue Apr 11, 2014
When using aufs in docker on coreos, obscure errors show up, such
as python's gevent not building for autoconf errors. Specifying
btrfs as the filesystem fixes it.
See moby/moby#2056
mboersma added a commit to deis/deis that referenced this issue Apr 15, 2014
When using aufs in docker on coreos, obscure errors show up, such
as python's gevent not building for autoconf errors. Specifying
btrfs as the filesystem fixes it.
See moby/moby#2056
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.