docksal: Windows 10: `fin project create` fails when cloning repo
Description
Running the fin project create command results in a fatal error, preventing the creation of the project directory.
Steps to reproduce the issue:
- Launch WSL
- Navigate to your parent docksal “Projects” directory
fin project create- When prompted, provide a project name. I used
devdivinityWhat would I like to install?3. Drupal 7Proceed with cloning confirmation: [ y ]
Describe the results you received:
1. Name your project (lowercase alphanumeric, underscore, and hyphen): devdivinity
2. What would you like to install?
PHP based
1. Drupal 8
2. Drupal 8 (Composer Version)
3. Drupal 7
4. Wordpress
5. Magento
6. Laravel
7. Symfony Skeleton
8. Symfony WebApp
9. Grav CMS
10. Backdrop CMS
Go based
11. Hugo
JS based
12. Gatsby JS
HTML
13. Static HTML site
Enter your choice (1-13): 3
Project folder: /c/Users/kds38/Projects/devdivinity
Project software: Drupal 7
Project URL: http://devdivinity.docksal
Do you wish to proceed? [y/n]: y
Cloning repository...
Cloning into 'devdivinity'...
error: invalid config file /var/www/devdivinity/.git/config
fatal: could not set 'core.filemode' to 'false'
Checkout finished with errors. Do you wish to continue? [y/n]: n
Describe the results you expected:
A new functional Drupal-7 based project
Output of fin config:
fin config
---------------------
COMPOSE_PROJECT_NAME_SAFE: projects
COMPOSE_FILE:
C:/Users/kds38/.babun/cygwin/home/kds38/.docksal/stacks/volumes-bind.yml
C:/Users/kds38/.babun/cygwin/home/kds38/.docksal/stacks/stack-default.yml
C:/Users/kds38/Projects/.docksal/docksal.yml
ENV_FILE:
C:/Users/kds38/Projects/.docksal/docksal.env
PROJECT_ROOT: /c/Users/kds38/Projects
DOCROOT: docroot
VIRTUAL_HOST: projects.docksal
VIRTUAL_HOST_ALIASES: *.projects.docksal
IP: 192.168.64.100
MYSQL:
Docker Compose configuration
---------------------
---------------------
Output of fin sysinfo:
fin sysinfo output
███ OS
Cygwin Windows 10.0.17134
CYGWIN_NT-10.0-WOW TTS-170241WL 2.11.2(0.329/5/3) 2018-11-08 14:30 i686 Cygwin
███ ENVIRONMENT
MODE : VirtualBox VM
DOCKER_HOST : tcp://192.168.64.100:2376
███ FIN
fin version: 1.80.1
███ DOCKER COMPOSE
EXPECTED VERSION: 1.23.1
docker-compose version 1.23.1, build b02f1306
docker-py version: 3.5.0
CPython version: 3.6.6
OpenSSL version: OpenSSL 1.0.2o 27 Mar 2018
███ DOCKER
EXPECTED VERSION: 18.06.1-ce
Client:
Version: 18.06.1-ce
API version: 1.38
Go version: go1.10.3
Git commit: e68fc7a
Built: Tue Aug 21 17:21:34 2018
OS/Arch: windows/amd64
Experimental: false
Server:
Engine:
Version: 18.06.1-ce
API version: 1.38 (minimum version 1.12)
Go version: go1.10.3
Git commit: e68fc7a
Built: Tue Aug 21 17:28:38 2018
OS/Arch: linux/amd64
Experimental: false
███ DOCKER MACHINE
EXPECTED VERSION: 0.15.0
docker-machine.exe version 0.15.0, build b48dc28d
NAME ACTIVE DRIVER STATE URL SWARM DOCKER ERRORS
docksal * virtualbox Running tcp://192.168.64.100:2376 v18.06.1-ce
███ DOCKSAL: PROJECTS
project STATUS virtual host project root
finupdate Up 2 hours finupdate.docksal,*.finupdate.docksal,finupdate.docksal.* /c/Users/kds38/Projects/finupdate
███ DOCKSAL: VIRTUAL HOSTS
*.finupdate.docksal
finupdate.docksal.*
finupdate.docksal
███ DOCKER: RUNNING CONTAINERS
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
a93f30c4bc3f docksal/web:2.1-apache2.4 "httpd-foreground" 3 hours ago Up 2 hours 80/tcp, 443/tcp finupdate_web_1_b428c66a272d
6c76761f096b docksal/cli:2.5-php7.1 "/opt/startup.sh sup…" 3 hours ago Up 2 hours (healthy) 22/tcp, 3000/tcp, 9000/tcp finupdate_cli_1_200ee601f513
2afcb7ba45b0 docksal/db:1.2-mysql-5.6 "/entrypoint.sh mysq…" 3 hours ago Up 2 hours 0.0.0.0:32768->3306/tcp finupdate_db_1_9edb6f3a05be
39920c45873d docksal/ssh-agent:1.2 "docker-entrypoint.s…" 21 hours ago Up 2 hours (healthy) docksal-ssh-agent
bc6f7b6340f4 docksal/dns:1.1 "docker-entrypoint.s…" 21 hours ago Up 2 hours (healthy) 192.168.64.100:53->53/udp docksal-dns
d85fc7773c06 docksal/vhost-proxy:1.4 "docker-entrypoint.s…" 21 hours ago Up 2 hours (healthy) 192.168.64.100:80->80/tcp, 192.168.64.100:443->443/tcp docksal-vhost-proxy
███ DOCKER: NETWORKS
NETWORK ID NAME DRIVER SCOPE
49bdc284fd08 _default bridge local
419e58770eb8 bridge bridge local
cf7a5ea93a5b finupdate_default bridge local
45c6d70d91d3 host host local
be17984b4714 none null local
███ VIRTUALBOX
EXPECTED VERSION: 5.2.20
5.2.20r125813
███ DOCKSAL MOUNTS
//192.168.64.1/docksal-c on /c type cifs (rw,relatime,vers=2.1,sec=ntlmssp,cache=strict,username=kds38,domain=WIN,uid=0,noforceuid,gid=0,noforcegid,addr=192.168.64.1,file_mode=0777,dir_mode=0777,nounix,serverino,mapposix,nobrl,mfsymlinks,noperm,rsize=1048576,wsize=1048576,echo_interval=60,actimeo=1)
//192.168.64.1/docksal-c on /mnt/sda1/var/lib/docker/volumes/finupdate_project_root/_data type cifs (rw,relatime,vers=2.1,sec=ntlmssp,cache=strict,username=kds38,domain=WIN,uid=0,noforceuid,gid=0,noforcegid,addr=192.168.64.1,file_mode=0777,dir_mode=0777,nounix,serverino,mapposix,nobrl,mfsymlinks,noperm,rsize=1048576,wsize=1048576,echo_interval=60,actimeo=1)
███ HDD Usage
Filesystem Size Used Available Use% Mounted on
/dev/sda1 46.1G 2.5G 41.2G 6% /mnt/sda1
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 25 (14 by maintainers)
Yeah basically everything looks right on your main one. The problem is in git. Project create clones repo using
fin run-cli git.... It fails for you regardless of the repo and even with--cleanoption that should ignore ay leftovers on the home volume, meaning that it’s not therun-clior specific repo to blame.And I do not see a single reason why it would fail like that, given that permissions are fine and
fin run-clican write files just fine in that dir.The error itself is also more usual on windows, which can fail to set filemode. But
run-cliis actually a Linux container and git runs inside it, so it should not fail to set filemode.I am out of guesses at the moment and don’t know what to check for the root cause next. As a last guess I would run
But they will probably fail in the same way.
I would recommend you run
fin run-cli --clean bash -ion your main one to run interactive bash session, and play with cloning different repos there and try to pinpoint where the issues with git come from.