Why does docker mount a file with a numeric value as a directory?

Running a docker run command with:

-v=/path/to/file/name0.conf:/etc/name.conf

was resulting in the docker container not being started:

  • “Official” docker backup strategy - what about consistency?
  • Download BAIR-trained Caffe Model Using Script
  • Why is the Kafka distributed connector dying when the node I created it on is killed?
  • Run asp.net 4.5 in Docker
  • Connecting to Docker container connection refused - but container is running
  • plugin/docker : Is passing id_rsa priv key using build_args correct?
  • docker: Error response from daemon: Cannot start container <hash>: [9] System error: not a directory.
    

    Why is this file not mounting in Docker?

    I can make the name nameA.conf and mount it fine. The file nameA.conf and name0.conf are identical (verified with diff), have the same rights (verified with ls -l).


    docker --version
    Docker version 1.10.1, build 9e83765
    

  • Emails not working in Linux Containers
  • Docker: using Using --volumes-from to backup data files
  • Host port with DB to Docker container
  • cannot connect to service hosted in ECS built through cloudformation template
  • How to use volumes-from in marathon
  • Why can't I extend docker postgres image to create extra database and user
  • One Solution collect form web for “Why does docker mount a file with a numeric value as a directory?”

    Docker does not mount files ending in numeric characters in their name correctly into containers.

    It converts the file into a directory because of the 0 in the name – this can be reproduced with different filenames that are similar and have numeric characters.

    The solution is to use non-numeric characters in the filename locally.

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.