depot tools inside a windows container doesn't bootstrap cipd_client.exe correctly
Reported by
p...@tokbox.com,
Aug 14 2017
|
||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13) AppleWebKit/605.1.2 (KHTML, like Gecko) Version/11.1 Safari/605.1.2 Steps to reproduce the problem: 1. Create a folder with the attached Dockerfile.depottools (rename to Dockerfile) 2. docker build depot-tools . 3. docker run --rm -it depot-tools 4. Run "gclient" What is the expected behavior? gclient to behave normally (install dependencies and then show usage info) What went wrong? '"C:\depot_tools\.cipd_client.exe"' is not recognized as an internal or external command, operable program or batch file. '"C:\depot_tools\.cipd_client.exe"' is not recognized as an internal or external command, operable program or batch file. 'python' is not recognized as an internal or external command, operable program or batch file. Did this work before? N/A Chrome version: n/a Channel: n/a OS Version: 2016 Flash Version: If I run depot_tools\cipd before ever running gclient, then it prints a message about bootstrapping cipd client, and once it returns, gclient behaves as expected. If gclient is run first, running depot_tools\cipd returns immediately (no log output) and gclient continues to not work.
,
Sep 14
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||
►
Sign in to add a comment |
||
Comment 1 by kkaluri@chromium.org
, Sep 14 2017