question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Doesn't work with special chars in path

See original GitHub issue

Not working:

Správca@gadelat-pc MINGW64 ~/Documents/feed/docker2 (stats)
$ pwd
/c/Users/Správca/Documents/feed/docker2

Správca@gadelat-pc MINGW64 ~/Documents/feed/docker2 (stats)
$ docker-compose build
Building adminer
Traceback (most recent call last):
  File "<string>", line 3, in <module>
  File "C:\projects\compose\compose\cli\main.py", line 54, in main
  File "C:\projects\compose\compose\cli\docopt_command.py", line 23, in sys_disp     atch
  File "C:\projects\compose\compose\cli\docopt_command.py", line 26, in dispatch
  File "C:\projects\compose\compose\cli\main.py", line 171, in perform_command
  File "C:\projects\compose\compose\cli\main.py", line 192, in build
  File "C:\projects\compose\compose\project.py", line 235, in build
  File "C:\projects\compose\compose\service.py", line 683, in build
  File "c:\projects\compose\venv\lib\site-packages\docker\api\build.py", line 41     , in build
TypeError: You must specify a directory to build in path
docker-compose returned -1

After copying, this issue no longer exists (another problem occured, but that’s another issue I guess):

Správca@gadelat-pc MINGW64 /c/Downloads/feed/docker2 (stats)
$ pwd
/c/Downloads/feed/docker2

Správca@gadelat-pc MINGW64 /c/Downloads/feed/docker2 (stats)
$ docker-compose build
Building adminer
Couldn't connect to Docker daemon - you might need to run `docker-machine start default`.

Issue Analytics

  • State:closed
  • Created 8 years ago
  • Comments:12

github_iconTop GitHub Comments

3reactions
osariscommented, Mar 30, 2016

I changed my account folder to C:\Raphael and it works.

0reactions
ostroluckycommented, Nov 3, 2018

Ah ok that makes sense. I’m not going to have access to windows machine for a while so I think we can close it until someone here will report this again.

What might have been the issue anyway that that you are confident this is fixed?

Read more comments on GitHub >

github_iconTop Results From Across the Web

Including a script does not work when path has special ...
Moving it to some other path without special characters in the name works fine. How can such a case be catered while using...
Read more >
read_*() does not work for special characters in file path #371
I can't provide a reprex, I think, but the message should be clear. The problem occurs when the file path contains, e.g., German...
Read more >
biblatex - Windows path to LocalTexFiles can't contain special ...
The work around was to use another one, with no special characters: D:\Users\Varios\LocalTexFiles (in both cases, bib files contain only regular ...
Read more >
Special Characters You Should Avoid Using and File Path ...
Unacceptable. The following characters are considered reserved, and should not be used in any of the above examples. Character, Name.
Read more >
VS unable to open project with some special characters in the ...
Previous version of VS 2017 was able to open a solution with special characters in the path. Example: c:\project\folder\Some%20- 520ugly%20path\.sln
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found