Docker - unable to prepare context: unable to evaluate symlinks in Dockerfile path: GetFileAttributesEx

Question

I just downloaded Docker Toolbox for Windows 10 64-bit today. I'm going through the tutorial. I'm receiving the following error when trying to build an image using a Dockerfile.

Steps:

Launched Docker Quickstart terminal.
testdocker after creating it.
Prepare Dockerfile as documented in "Build your own image" web link
ran the below command

docker build -t docker-whale .

Error: $ docker build -t docker-whale .

unable to prepare context: unable to evaluate symlinks in Dockerfile path: GetFileAttributesEx C:\Users\Villanueva\Test\testdocker\Dockerfile: The system cannot find the file specified.

BTW: I tried several options mentioned @ https://github.com/docker/docker/issues/14339

docker info

Output:

Containers: 4
 Running: 0
 Paused: 0
 Stopped: 4
Images: 2
Server Version: 1.10.1
Storage Driver: aufs
 Root Dir: /mnt/sda1/var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 20
 Dirperm1 Supported: true
Execution Driver: native-0.2
Logging Driver: json-file
Plugins:
 Volume: local
 Network: bridge null host
Kernel Version: 4.1.17-boot2docker
Operating System: Boot2Docker 1.10.1 (TCL 6.4.1); master : b03e158 - Thu Feb 11 22:34:01 UTC 2016
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 996.2 MiB
Name: default
ID: C7DS:CIAJ:FTSN:PCGD:ZW25:MQNG:H3HK:KRJL:G6FC:VPRW:SEWW:KP7B
Debug mode (server): true
 File Descriptors: 32
 Goroutines: 44
 System Time: 2016-02-19T17:37:37.706076803Z
 EventsListeners: 0
 Init SHA1:
 Init Path: /usr/local/bin/docker
 Docker Root Dir: /mnt/sda1/var/lib/docker
Labels:
 provider=virtualbox

Update: docker build -t XXX **--file** ./Dockefile . worked. Docker may want to update their documentation for Windows users. — villanux, Feb 19 '16 at 19:09
If `docker build -t XXX --file ./Dockefile` it might be because you got the filename wrong it's missing the R. — eXa, May 09 '16 at 11:14
This is an amazingly bad error message, it just means "cannot open file" - same on Linux and macOS. — RichVel, Dec 19 '16 at 09:42

score 336 · Answer 1 · edited Dec 12 '22 at 22:04

336

While executing the following command,

docker build -t docker-whale .

check that Dockerfile is present in your current working directory.

edited Dec 12 '22 at 22:04

Peter Mortensen

30,738
21
105
131

answered Jul 14 '16 at 10:00

kalyani chaudhari

7,515
3
24
21

34

Thanks. My issue was I had created my Dockerfile in Notepad and it had automatically appended .txt to the filename. – IanGSY Nov 15 '16 at 09:07
17

You may also explicitly write the Dockerfile name with the `f`flag, as in `docker build -f Dockerfile-dev.yaml -t my_container .` This may prove useful if you have several Dockerfile in your project, one per environment, for example. The same applies to docker-compose. Putting them in different subdirectories will not work, since the context (`.`) will not match. – Sumi Straessle Feb 17 '17 at 08:16
1

@IanGSY I wish I could give you more points for that. That was exactly my problem too! – K. Brafford Nov 12 '17 at 05:57
11

Notepad is an excessively evil program. – Per Lundberg Dec 29 '17 at 08:18
When you need a reminder that you're calling from the wrong directory xD – Kraken Jan 28 '21 at 11:27
Copied something weird after the trailing period, removing this helped. – Christopher Markieta Feb 10 '21 at 22:49
Well, I have it in my current dir but still have the error. – Toma Tomov Jul 21 '22 at 20:28
Your Expansion really makes sense. my file was called `docker`, which led to this error but your solution was really helpful. big ups – Benjamin Andoh Aug 15 '22 at 11:41

score 241 · Answer 2 · edited Dec 12 '22 at 23:10

241

The error message is misleading

The problem has nothing to do with symbolic links really. Usually, the problem is only that Docker cannot find the Dockerfile describing the build.

Typical reasons are these:

Dockerfile has wrong name. It must be called Dockerfile. If it is called, for instance, dockerfile, .Dockerfile, Dockerfile.txt, or other, it will not be found.
Dockerfile is not in context. If you say docker build contextdir, the Dockerfile must be at contextdir/Dockerfile. If you have it in, say, ./Dockerfile instead, it will not be found.
Dockerfile does not exist at all. Does it sound silly? Well, I got the above error message from my GitLab CI after I had written a nice Dockerfile, but I had forgotten to check it in. Silly? Sure. Unlikely? No.

edited Dec 12 '22 at 23:10

Peter Mortensen

30,738
21
105
131

answered Aug 30 '19 at 09:47

Lutz Prechelt

36,608
11
63
88

Additional tip that solved my problem with the same message: be sure to have your CaSinG correct. For Directory path as well as the Dockerfile. Since linux is pretty picky about that. – RaimondB Jul 03 '20 at 19:57
4

Filename did the trick for me. I had to change DockerFile to `Dockerfile` – Junaid Nov 25 '20 at 07:51
2

Likewise, check for simple spelling errors. I landed here because `Dockefile` is certainly not the same as `Dockerfile` :facepalm: Since building with `docker build -f .` worked, I looked closer and realized I had mistyped it. – Saites Dec 20 '20 at 21:27

score 48 · Answer 3 · edited Dec 12 '22 at 22:34

48

If you are working on Windows 8, you would be using Docker toolbox.

From the mydockerbuild directory, run the below command as your Dockerfile is a textfile:

docker build -t docker-whale -f ./Dockerfile.txt .

edited Dec 12 '22 at 22:34

Peter Mortensen

30,738
21
105
131

answered Mar 02 '17 at 05:53

Divyanshu sachdeva

673
6
19

4

for future reference if you need to do this it is because your Dockerfile has an extension whereas by default Docker expects it not too. Setting the file manually with the extension adds headaches you do not need. You should set Windows explorer to show extensions and then remove the extension. – Alex Dec 11 '17 at 19:08
if you're following along on the docker documentation "getting started" tutorial you would use this: `docker build -t friendlyhello -f ./Dockerfile.txt .` – Mike Kellogg Jan 31 '18 at 03:23
Its really bad semantics that you have to specify the file name and the dummy path also. and/or always name your file as Dockerfile.. :-( – myloginid Mar 26 '18 at 06:20
This saved my day. By the way, I'm using a Mac machine. But the catch here is that the Dockerfile was created a plain text file. Thanks buddy for the help. – Sachidananda Naik Sep 14 '19 at 20:06

SharpCoder · Answer 4 · 2019-04-24T18:18:02.823

29

The name of the file should be Dockerfile and not .Dockerfile. The file should not have any extension.

edited Apr 24 '19 at 18:18

answered Mar 27 '19 at 15:56

SharpCoder

18,279
43
153
249

score 28 · Answer 5 · answered Mar 09 '21 at 07:40

28

Make sure you moved to the directory where Dockerfile is located.
Make sure your Dockerfile is extension-less. That is, not Dockerfile.txt, Dockerfile.rtf, or any other.
Make sure you named Dockerfile, and not DockerFile, dockerfile or any other.

answered Mar 09 '21 at 07:40

Vijayakumar Pattanashetti

319
3
4

big help on the `Dockerfile` instead of `DockerFile` – Ukrainian-serge Apr 06 '22 at 16:22

score 20 · Answer 6 · answered Jan 09 '17 at 22:57

20

I had named my file dockerfile instead of Dockerfile (capitalized), and once I changed that, it started processing my "Dockerfile".

answered Jan 09 '17 at 22:57

Alan Fitzgerald

192
1
7

1

I cloned a json file instead of creating a new file. Once i renamed it to Dockerfile and updated it contents, it didn't show .json extension and later realised thats the culprit! Thanks for the note! – Ayyappa Aug 01 '20 at 17:09

score 16 · Answer 7 · edited Dec 12 '22 at 22:13

16

Just remove the extension .txt from Dockerfile and run the command

docker build -t image-name

It will work for sure.

edited Dec 12 '22 at 22:13

Peter Mortensen

30,738
21
105
131

answered Feb 13 '17 at 15:10

Satyam

160
1
3

score 11 · Answer 8 · edited Dec 12 '22 at 22:34

11

I have got this error (in a MacBook) though I used the correct command to create the image,

docker build -t testimg .

Later I found that the path is the problem. Just navigate to the correct path that contains the Docker file. Just double check your current working directory. Nothing to panic about!

edited Dec 12 '22 at 22:34

Peter Mortensen

30,738
21
105
131

answered Nov 08 '17 at 19:15

codeX

4,842
2
31
36

score 6 · Answer 9 · edited Sep 28 '21 at 02:38

6

This command worked for me:

docker build -t docker-whale -f Dockerfile.txt .

edited Sep 28 '21 at 02:38

Pang

9,564
146
81
122

answered Aug 13 '19 at 15:48

AMAN BHARDWAJ

79
1
5

1

Dockerfile is not a .txt file. If you have it as a .txt file it will give error again. – Donald Shahini Nov 20 '19 at 07:21

score 5 · Answer 10 · edited Dec 12 '22 at 22:12

5

That's just because Notepad add ".txt" at the end of Dockerfile.

edited Dec 12 '22 at 22:12

Peter Mortensen

30,738
21
105
131

answered Feb 04 '17 at 17:34

Aurélien

61
1
1

And Windows hides it? – Peter Mortensen Dec 12 '22 at 22:10

score 4 · Answer 11 · edited Dec 12 '22 at 22:47

4

I had created my DockerFile by the Visual Studio 2017 Docker Support tool and had the same error.

After a while, I realised I was not in the correct directory that contains the Dockerfile (~\source\repos\DockerWebApplication\). I cd'ed to the correct file (~/source/repos/DockerWebApplication/DockerWebApplication) which was inside the project and successfully created the Docker image.

edited Dec 12 '22 at 22:47

Peter Mortensen

30,738
21
105
131

answered Nov 25 '18 at 12:33

Hasan

1,243
12
27

*DockerFile* is the wrong file name. It should be *Dockerfile*. – Peter Mortensen Dec 12 '22 at 22:45

score 4 · Answer 12 · edited Dec 12 '22 at 23:00

In WSL, there seems to be a problem with path conversion. The location of the Dockerfile in Ubuntu (where I'm running Docker and where Dockerfile lives) is "/home/sxw455/App1", but neither of these commands worked:

$ pwd

/home/sxw455/App1

$ ll

total 4
drwxrwxrwx 0 sxw455 sxw455 4096 Dec 11 19:28 ./
drwxr-xr-x 0 sxw455 sxw455 4096 Dec 11 19:25 ../
-rwxrwxrwx 1 sxw455 sxw455  531 Dec 11 19:26 Dockerfile*
-rwxrwxrwx 1 sxw455 sxw455  666 Dec 11 19:28 app.py*
-rwxrwxrwx 1 sxw455 sxw455   12 Dec 11 19:27 requirements.txt*

$ docker build -t friendlyhello .

unable to prepare context: unable to evaluate symlinks in Dockerfile path: GetFileAttributesEx C:\Windows\System32\Dockerfile: The system cannot find the file specified.

$ docker build -t friendlyhello "/home/sxw455/App1"
unable to prepare context: path "/home/sxw455/App1" not found

But in Windows, the actual path is:

C:\Users\sxw455\AppData\Local\Packages\CanonicalGroupLimited.Ubuntu18.04onWindows_79rhkp1fndgsc\LocalState\rootfs\home\sxw455\App1

And so I had to do this (even though I ran it from Bash):

$ docker build -t friendlyhello

"C:\Users\sxw455\AppData\Local\Packages\CanonicalGroupLimited.Ubuntu18.04onWindows_79rhkp1fndgsc\LocalState\rootfs\home\sxw455\App1"

Sending build context to Docker daemon   5.12kB
Step 1/7 : FROM python:2.7-slim
 ---> 0dc3d8d47241
Step 2/7 : WORKDIR /app
 ---> Using cache
 ---> f739aa02ce04
Step 3/7 : COPY . /app
 ---> Using cache
 ---> 88686c524ae9
Step 4/7 : RUN pip install --trusted-host pypi.python.org -r requirements.txt
 ---> Using cache
 ---> b95f02b14f78
Step 5/7 : EXPOSE 80
 ---> Using cache
 ---> 0924dbc3f695
Step 6/7 : ENV NAME World
 ---> Using cache
 ---> 85c145785b87
Step 7/7 : CMD ["python", "app.py"]
 ---> Using cache
 ---> c2e43b7f0d4a
Successfully built c2e43b7f0d4a
Successfully tagged friendlyhello:latest
SECURITY WARNING: You are building a Docker image from Windows against a non-Windows Docker host. All files and directories added to build context will have '-rwxr-xr-x' permissions. It is recommended to double check and reset permissions for sensitive files and directories.

I had similar problems with environment variables during the initial installation, and followed some advice that said to install the Windows DockerCE and hack the environment variables rather than installing the Ubuntu DockerCE, because (I hope I remembered this correctly) that WSL does not fully implement systemctl. Once the Windows Docker CE installation is done and environment variables are set, docker then works fine under WSL/Ubuntu.

This worked for me! I only installed Docker Toolbox and didn't install it in WSL; instead, I'm using the windows executables directly, since WSL can do that now. — Lawrence Lee, Jan 02 '19 at 00:50

score 3 · Answer 13 · edited Dec 12 '22 at 22:09

3

In Windows 10, period is the first parameter:

docker build . -t docker-whale

edited Dec 12 '22 at 22:09

Peter Mortensen

30,738
21
105
131

answered Nov 04 '16 at 13:03

PDA

766
6
10

14

not anymore (if ever) `docker build -t docker-whale .` is a valid command – sebagomez Jun 20 '17 at 01:16

PontiusTheBarbarian · Answer 14 · 2020-01-13T15:09:04.183

Two ways to build a dockerfile:

You can decide not to specify the file name of which to build from and just build it specifying a path (doing it this way the file name must be Dockerfile with no extension appended, eg: docker build -t docker-whale:tag path/to/Dockerfile

or

You can specify a file with -f and it doesn't matter what extension (within reason .txt, .dockerfile, .Dockerfile etc..) you decide to use, eg docker build -t docker-whale:tag /path/to/file -f docker-whale.dockerfile.

score 3 · Answer 15 · answered Jul 14 '20 at 08:38

The error means that docker build is either using a PATH | URL that are incorrectly input or that the Dockerfile cannot be found in the current directory. Also, make sure that when running the command from an integrated terminal (e.g. bash inside your IDE or text editor) you have the admin permissions to do so. Best if you can check the PATH from your terminal with pwd (in bash shell or dir if using a simple cli on windows) and copy the exact path where you want the image to be build.

docker build C:\windows\your_amazing_directory

docker build --help will also show you available options to use in case of malformed or illegal commands.

score 2 · Answer 16 · edited Dec 12 '22 at 22:26

2

I had originally created my Dockerfile in PowerShell and though I didn't see an extension on the file it showed as a PS File Type...once I created the file from Notepad++ being sure to select the "All types (.)" File Type with no extension on the File Name (Dockerfile). That allowed my image build command to complete successfully...Just make sure your Dockerfile has a Type of "File"...

edited Dec 12 '22 at 22:26

Peter Mortensen

30,738
21
105
131

answered Jun 23 '17 at 13:32

Helper7123

21
1

score 2 · Answer 17 · edited Dec 12 '22 at 22:38

2

The problem is that the file name should be Dockerfile and not DockerFile or dockerfile. It should be D capital followed by ockerfile in lowercase. Please note.

edited Dec 12 '22 at 22:38

Peter Mortensen

30,738
21
105
131

answered May 23 '18 at 10:21

vincent

21
2

score 2 · Answer 18 · edited Dec 12 '22 at 23:05

2

I my case (run from Windows 10):

Rename the file myDockerFile.Dockerfile to Dockerfile (without file extension).

Then run this command from outside the folder:

docker build .\Docker-LocalNifi\

This is working for me and for my colleagues at work.

edited Dec 12 '22 at 23:05

Peter Mortensen

30,738
21
105
131

answered Apr 02 '19 at 08:57

Yohan

1,173
11
16

score 2 · Answer 19 · answered Nov 13 '19 at 10:30

2

Be sure your DOCKERfile is in the ROOT of the application directory, I had mine in src which resulted in this error because Docker was not finding the path to DOCKERfile

answered Nov 13 '19 at 10:30

Frank Odoom

1,545
18
19

Is this a bogus answer? The name of the file is *Dockerfile*, not *DOCKERfile*. – Peter Mortensen Dec 12 '22 at 23:16

score 2 · Answer 20 · answered Dec 03 '22 at 19:56

2

Installing docker.io instead of docker helped me

i.e.

apt install docker.io

answered Dec 03 '22 at 19:56

Tomer Gal

933
12
21

What is *"docker.io"*? – Peter Mortensen Dec 12 '22 at 23:29
*[What is docker.io in relation to docker-ce and docker-ee (now called "Mirantis Kubernetes Engine")?](https://stackoverflow.com/questions/45023363/what-is-docker-io-in-relation-to-docker-ce-and-docker-ee-now-called-mirantis-k)* – Peter Mortensen Dec 12 '22 at 23:32

score 1 · Answer 21 · edited Dec 12 '22 at 22:18

1

To build Dockerfile, save the automated content in Dockerfile. Not Dockerfile because while opening a file command:

notepad Dockerfile

(A text file is written so the file cannot build.)

To build the file, run:

notepad Dockerfile

and now run:

docker build -t docker-whale .

Make sure you are in the current directory of Dockerfile.

edited Dec 12 '22 at 22:18

Peter Mortensen

30,738
21
105
131

answered Feb 16 '17 at 06:05

niteshkumarmodi

25
1
10

What do you mean by the first part? That file *Dockerfile* can not be changed while it is open in [Notepad](https://en.wikipedia.org/wiki/Notepad_%28software%29)? – Peter Mortensen Dec 12 '22 at 22:20

score 1 · Answer 22 · edited Dec 12 '22 at 23:03

1

Most importantly, make sure your file name is Dockerfile. If you use another name it won't work (at least it did not for me).

Also if you are in the same directory where the Dockerfile is use a ., i.e.,

docker build -t Myubuntu1:v1 .

Or use the absolute path, i.e.,

docker build -t Myubuntu1:v1 /Users/<username>/Desktop/Docker

edited Dec 12 '22 at 23:03

Peter Mortensen

30,738
21
105
131

answered Jan 28 '19 at 12:27

ady6831983

113
1
8

score 1 · Answer 23 · edited Dec 12 '22 at 23:07

1

Make sure file name "Dockerfile" is not saved with any extension. Just create a file without any extension.

And make sure Dockerfile is in the same directory from where you are trying to build the Docker image.

edited Dec 12 '22 at 23:07

Peter Mortensen

30,738
21
105
131

answered Apr 16 '19 at 05:00

Nakesh

546
2
7
8

score 1 · Answer 24 · edited Dec 12 '22 at 23:19

1

In case if we have multiple Docker files in our environment just Dockerfile won’t suffice for our requirement.

docker build -t ihub -f Dockerfile.ihub .

So use the file (-f argument) command to specify your docker file (Dockerfile.ihub).

edited Dec 12 '22 at 23:19

Peter Mortensen

30,738
21
105
131

answered May 08 '20 at 07:26

chethan bhounsley g

129
1
10

It's also necessary to have the `.` (dot) at the end of the line, as the above shows. – Purplejacket Jul 10 '20 at 02:22
Documentation for `docker build` is here: https://docs.docker.com/engine/reference/commandline/build/ – Purplejacket Jul 10 '20 at 02:23

score 1 · Answer 25 · answered Sep 08 '20 at 15:26

1

Make sure you run the command

docker build . -t docker-whale

from the directory that has the dockerfile

answered Sep 08 '20 at 15:26

Babatunde Mustapha

2,131
20
21

This seems to be repeat of previous answers. – Peter Mortensen Dec 12 '22 at 23:25

score 0 · Answer 26 · edited Dec 12 '22 at 22:24

0

I got this on Windows when the path I was working in was under a junction point directory. So my fix was to not work under that path.

edited Dec 12 '22 at 22:24

Peter Mortensen

30,738
21
105
131

answered May 16 '17 at 21:25

Chris F Carroll

11,146
3
53
61

score 0 · Answer 27 · edited Dec 12 '22 at 22:35

0

On Mac it works for the below command (I hope your .Dockerfile is in your root directory).

docker build -t docker-whale -f .Dockerfile .

edited Dec 12 '22 at 22:35

Peter Mortensen

30,738
21
105
131

answered May 14 '18 at 06:17

caldera.sac

4,918
7
37
69

score 0 · Answer 28 · edited Dec 12 '22 at 22:42

0

The issue is related to the DockerFile creation procedure.

In order to work, open cmd, cd to the directory of interest and type:

abc>DockerFile

This will create a file called DockerFile inside your folder.

Now type:

notepad DockerFile

This will open the DockerFile file in Notepad and you will have to copy/paste the standard code provided.

Save the file and now, finally, build your image with Docker typing:

docker build -t docker-whale .

This is working for me.

edited Dec 12 '22 at 22:42

Peter Mortensen

30,738
21
105
131

answered Oct 31 '18 at 12:32

Employee

3,109
5
31
50

What is 'abc'? Wouldn't that result in "command not found" (to standard error)? – Peter Mortensen Dec 12 '22 at 22:40
Is this a bogus answer? *DockerFile* is the wrong file name. It should be *Dockerfile*. – Peter Mortensen Dec 12 '22 at 22:44

score 0 · Answer 29 · answered May 14 '20 at 13:57

0

I erroneously created Dockerfile.txt in my working directory leading to the above-mentioned error while build

The fix was to remove the .txt extension from the file.

The file name should be Dockerfile only without any extension.

answered May 14 '20 at 13:57

iCantC

2,852
1
19
34

score 0 · Answer 30 · answered May 28 '20 at 17:51

Execute docker build -t getting-started . in your project directory and make sure Dockerfile is present and having no .txt extension. If you are on Windows, check the 'file name extension' in the under the view tab in the File Explorer to show whether .txt is there or not and remove it if the former is true. Good Luck.

score 0 · Answer 31 · edited Dec 12 '22 at 23:21

0

I also faced the same issues, and it was resolved when I created a file named with DockerFile and mentioned all the commands which wanted to get executed during creation of the image.

edited Dec 12 '22 at 23:21

Peter Mortensen

30,738
21
105
131

answered Jun 06 '20 at 14:28

Yoshita Mahajan

443
4
6

But it isn't *DockerFile*. It is *Dockerfile*. Is this just repeating some of the incorrect answers? – Peter Mortensen Dec 12 '22 at 23:21

score 0 · Answer 32 · answered Aug 13 '20 at 10:47

0

If you have mounted a second drive to an NTFS folder as a 'mounted volume' then you can get this issue.

Move you files to a drive location outside of the mounted volume.

answered Aug 13 '20 at 10:47

Greg Domjan

13,943
6
43
59

Why is that a problem? What is the mechanism? – Peter Mortensen Dec 12 '22 at 23:23
@PeterMortensen See more here https://github.com/docker/for-win/issues/8110#issuecomment-723469794 – Greg Domjan Dec 13 '22 at 06:04

score 0 · Answer 33 · edited Dec 12 '22 at 23:24

0

Please check whether Docker is running on your Windows installation or not. I tried to find the solution and then accidentally checked and found the issue.

edited Dec 12 '22 at 23:24

Peter Mortensen

30,738
21
105
131

answered Aug 23 '20 at 20:28

Arun

601
10
15

score 0 · Answer 34 · edited Dec 12 '22 at 23:26

0

In Linux, folders are case sensitive.

I was getting this error because of the folder name TestAPI, and I was using TestApi.

edited Dec 12 '22 at 23:26

Peter Mortensen

30,738
21
105
131

answered Feb 08 '21 at 08:00

Gauravsa

6,330
2
21
30

score 0 · Answer 35 · answered Jul 26 '22 at 12:09

0

docker build -t docker-whale -f DockerFile .

answered Jul 26 '22 at 12:09

Selim Gencer

51
2

1

How is this different from the previous answers? What is it supposed to do? – Peter Mortensen Dec 12 '22 at 23:29

score 0 · Answer 36 · answered May 19 '23 at 13:29

0

The issue is in your GitHub workflow.

- uses: actions/checkout@v3  # <-- This is what you need to add 
- name: Build and Tag the Docker image
  run: docker build -t docker-whale .

answered May 19 '23 at 13:29

Fotios Tragopoulos

449
1
7
24

score 0 · Answer 37 · answered Jun 26 '23 at 15:04

0

For those using minikube image build, make sure that your .dockerignore does not include your Dockerfile.

answered Jun 26 '23 at 15:04

Cameron Hudson

3,190
1
26
38

score 0 · Answer 38 · answered Jul 27 '23 at 09:18

This issue can also happen when having trailing spaces after the backslash \ character, to reproduce the issue:

Create an empty Dockerfile
```
echo "FROM alpine" > Dockerfile
```
Run the build command - there's a trailing space after \, which causes the issue
```
docker build -t test \ 
-t another-tag .
```
Output of the above command:
```
ERROR: unable to prepare context: path " " not found
```
Fixed by removing the trailing space after \
```
docker build -t test \
-t another-tag .
```
Output - it works

score -1 · Answer 39 · edited Dec 12 '22 at 23:12

-1

To build an image from the command-line in Windows or Linux.

Create a Docker file in your current directory.

For example,

 FROM ubuntu
 RUN apt-get update
 RUN apt-get -y install apache2
 ADD . /var/www/html
 ENTRYPOINT apachectl -D FOREGROUND
 ENV name Devops_Docker

Don't save it with the .txt extension.
Under command-line run the command
```
 docker build . -t apache2image
```

edited Dec 12 '22 at 23:12

Peter Mortensen

30,738
21
105
131

answered Sep 28 '19 at 04:33

Udit Gandhi

337
4
6

Docker - unable to prepare context: unable to evaluate symlinks in Dockerfile path: GetFileAttributesEx

39 Answers39

The error message is misleading

Linked

Related