Docksal: Problems mounting shares with Docksal on Windows 10

Created on 10 Feb 2017  ·  69Comments  ·  Source: docksal/docksal

Fails on fin vm start
Error
Configuring SMB shares...
Enter your Windows account password:
Adding docker SMB share...
mount: mounting //192.168.64.1/c on /c failed: Permission denied
exit status 255
Error creating share.

Would appreciate any help yuo can give.

Regards
Ian

owindows 🏷bug
Source
picture ijf8090

All 69 comments

This is a duplicate of https://github.com/docksal/docksal/issues/115

We have a fix in the develop branch. Try DOCKSAL_VERSION=develop fin update --self, then fin vm restart

lmakarov picture lmakarov on 11 Feb 2017

Agree that this is a duplicate of #115. Have tried suggested fix, no change in behaviour.

Regards
Ian

ijf8090 picture ijf8090 on 11 Feb 2017

Please post the output from fin sysinfo here

lmakarov picture lmakarov on 11 Feb 2017

fin sysinfo
███ OS & BASICS
CYGWIN_NT-10.0-WOW DESKTOP-JUESE8H 1.7.35(0.287/5/3) 2015-03-04 12:07 i686 Cygwin
fin version: 1.0.2
Mode: VirtualBox VM
███ INSTANCES
NAME ACTIVE DRIVER STATE URL SWARM DOCKER ERRORS
docksal * virtualbox Running tcp://192.168.64.100:2376 v1.12.6
███ DOCKER
DOCKER_HOST: tcp://192.168.64.100:2376

Docker: Client:
Version: 1.12.6
API version: 1.24
Go version: go1.6.4
Git commit: 78d1802
Built: Wed Jan 11 00:23:16 2017
OS/Arch: windows/amd64

Server:
Version: 1.12.6
API version: 1.24
Go version: go1.6.4
Git commit: 78d1802
Built: Wed Jan 11 00:23:16 2017
OS/Arch: linux/amd64
███ DOCKER COMPOSE
Docker Compose: docker-compose version 1.9.0, build 2585387
docker-py version: 1.10.6
CPython version: 2.7.12
OpenSSL version: OpenSSL 1.0.2h 3 May 2016
███ DOCKER MACHINE
docker-machine.exe version 0.8.2, build e18a919
███ DOCKER: IMAGES
REPOSITORY TAG IMAGE ID CREATED SIZE
docksal/vhost-proxy 1.0 e3c362a38c4e 2 weeks ago 164.3 MB
docksal/dns 1.0 20c7a535479d 3 weeks ago 61.62 MB
docksal/ssh-agent 1.0 148220cc033d 3 weeks ago 12.22 MB
███ DOCKER: CONTAINERS
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
b89d4414ed68 docksal/ssh-agent:1.0 "/run.sh ssh-agent" 9 hours ago Up 3 minutes docksal-ssh-agent
4af34469a7c7 docksal/dns:1.0 "/opt/entrypoint.sh s" 9 hours ago Up 3 minutes 192.168.64.100:53->53/udp docksal-dns
0c7fdde71266 docksal/vhost-proxy:1.0 "/usr/local/bin/start" 9 hours ago Up 3 minutes 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp docksal-vhost-proxy
███ VIRTUALBOX
5.1.12r112440
███ NETWORK INTERFACES
Name: VirtualBox Host-Only Ethernet Adapter #3
GUID: 411c71b9-7cda-4240-8525-3aabbad25b6e
DHCP: Disabled
IPAddress: 192.168.64.1
NetworkMask: 255.255.255.0
IPV6Address: fe80:0000:0000:0000:39fe:d016:61b5:67f5
IPV6NetworkMaskPrefixLength: 64
HardwareAddress: 0a:00:27:00:00:36
MediumType: Ethernet
Status: Up
VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #3

Name: VirtualBox Host-Only Ethernet Adapter #2
GUID: 6f6700e1-5f77-4916-8582-cf2aea3c82ed
DHCP: Enabled
IPAddress: 192.168.64.101
NetworkMask: 255.255.255.0
IPV6Address: fe80:0000:0000:0000:01af:5eb8:e775:bde5
IPV6NetworkMaskPrefixLength: 64
HardwareAddress: 0a:00:27:00:00:09
MediumType: Ethernet
Status: Up
VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #2

Name: VirtualBox Host-Only Ethernet Adapter
GUID: de569415-861a-49ba-a66c-658add86672c
DHCP: Disabled
IPAddress: 192.168.56.1
NetworkMask: 255.255.255.0
IPV6Address: fe80:0000:0000:0000:b152:d3d4:52f3:0d34
IPV6NetworkMaskPrefixLength: 64
HardwareAddress: 0a:00:27:00:00:15
MediumType: Ethernet
Status: Up
VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter

███ MOUNTS
tmpfs on / type tmpfs (rw,relatime,size=917700k)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
devpts on /dev/pts type devpts (rw,relatime,mode=600,ptmxmode=000)
tmpfs on /dev/shm type tmpfs (rw,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
/dev/sda1 on /mnt/sda1 type ext4 (rw,relatime,data=ordered)
cgroup on /sys/fs/cgroup type tmpfs (rw,relatime,mode=755)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,relatime,cpuset)
cgroup on /sys/fs/cgroup/cpu type cgroup (rw,relatime,cpu)
cgroup on /sys/fs/cgroup/cpuacct type cgroup (rw,relatime,cpuacct)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,relatime,blkio)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,relatime,memory)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,relatime,net_cls)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,relatime,perf_event)
cgroup on /sys/fs/cgroup/net_prio type cgroup (rw,relatime,net_prio)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,relatime,hugetlb)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,relatime,pids)
/dev/sda1 on /mnt/sda1/var/lib/docker/aufs type ext4 (rw,relatime,data=ordered)
none on /mnt/sda1/var/lib/docker/aufs/mnt/5bd82c03de73bfe4bef40089a7ecdce0c6e45917883786692ae0bd434441c307 type aufs (rw,relatime,si=fa99e8c08d8682b2,dio,dirperm1)
none on /mnt/sda1/var/lib/docker/aufs/mnt/e5554b62f97c04cee7d0673b1dbf4d28a7ddeb61a4bb1b405e0826dbcb53e33b type aufs (rw,relatime,si=fa99e8c08db312b2,dio,dirperm1)
none on /mnt/sda1/var/lib/docker/aufs/mnt/dd5c9b4e12adafd2f577b2f2454411ad1cd48c63475180e13f42eacd95eacbec type aufs (rw,relatime,si=fa99e8c08d9682b2,dio,dirperm1)
shm on /mnt/sda1/var/lib/docker/containers/b89d4414ed68557dcc1616acb01f3542968d8680416e56484d60b613877b3b70/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=65536k)
shm on /mnt/sda1/var/lib/docker/containers/4af34469a7c7dc5580de64954a9a997a9c8039d6f802a734a25605040d372f17/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=65536k)
shm on /mnt/sda1/var/lib/docker/containers/0c7fdde71266265529b57eb2526afa12ba213089e7e59b4b82dee23a91fe965f/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=65536k)
nsfs on /var/run/docker/netns/f235e115362c type nsfs (rw)
nsfs on /var/run/docker/netns/392ea2b8eb64 type nsfs (rw)
nsfs on /var/run/docker/netns/871e0ca11dbe type nsfs (rw)
{ ~ } »

ijf8090 picture ijf8090 on 11 Feb 2017

After running DOCKSAL_VERSION=develop fin update --self fin version should be 1.0.5 - this is the one with the fix for this bug. Yours says fin version: 1.0.2.

Update fin using the develop branch and make sure it is v1.0.5

{ ~ }  » DOCKSAL_VERSION=develop fin update --self
Downloading https://raw.githubusercontent.com/docksal/docksal/develop/bin/fin
Done
{ ~ }  » fin -v
1.0.5

Remove the vm (just in case) and start it again

fin vm remove
fin vm start
lmakarov picture lmakarov on 12 Feb 2017

fin -v now shows 1.0.5 but still getting the same error on SMB share

ijf8090 picture ijf8090 on 13 Feb 2017

maybe fin fix-smb?

achekulaev picture achekulaev on 13 Feb 2017

Looks like you were playing with your adapters manually

Name: VirtualBox Host-Only Ethernet Adapter #2
GUID: 6f6700e1-5f77-4916-8582-cf2aea3c82ed
DHCP: Enabled
IPAddress: 192.168.64.101
NetworkMask: 255.255.255.0

This adapter should be deleted in VirtualBox UI. Then restart your vm with fin vm restart and it should be fine.

achekulaev picture achekulaev on 14 Feb 2017

@ijf8090 was your issue resolved?

achekulaev picture achekulaev on 16 Feb 2017

Sorry - have not been able to work on this (will get to it this weekend).

ijf8090 picture ijf8090 on 16 Feb 2017

Still seeing problem after I removed two VMs leaving only the docksal image. Also ran fin fix-smb - no change.
Thoughts?

ijf8090 picture ijf8090 on 17 Feb 2017

@ijf8090 https://github.com/docksal/docksal/issues/117#issuecomment-279561644 please try deleting network adapters. Deleting VM's won't cut it.

achekulaev picture achekulaev on 17 Feb 2017

Can't figure out how to do this on Windows 10 - do you have a link?

ijf8090 picture ijf8090 on 18 Feb 2017

@ijf8090
adapters

achekulaev picture achekulaev on 18 Feb 2017

@achekulaev,
I'm getting similar error on windows 10:

Configuring SMB shares...
Enter your Windows account password:
Adding docker SMB share...
mount: mounting //192.168.64.1/c on /c failed: Key has expired
exit status 255
Error creating share
Adding docker SMB share...mount: mounting //192.168.64.1/d on /d failed: Key has expired
exit status 255
Error creating share

fin sysinfo

{ ~ }  » fin sysinfo                                                                        ~ 127
███  OS & BASICS
CYGWIN_NT-10.0-WOW q16 1.7.35(0.287/5/3) 2015-03-04 12:07 i686 Cygwin
fin version: 1.1.0
Mode:  VirtualBox VM
███  INSTANCES
NAME      ACTIVE   DRIVER       STATE     URL                         SWARM   DOCKER    ERRORS
docksal   *        virtualbox   Running   tcp://192.168.64.100:2376           v1.13.1
███  DOCKER
DOCKER_HOST:    tcp://192.168.64.100:2376

time="2017-04-05T15:57:19+03:00" level=info msg="Unable to use system certificate pool: crypto/x509:                                                                                                                                          system root pool is not available on Windows"
Docker: Client:
 Version:      1.13.1
 API version:  1.26
 Go version:   go1.7.5
 Git commit:   092cba3
 Built:        Wed Feb  8 08:47:51 2017
 OS/Arch:      windows/amd64

Server:
 Version:      1.13.1
 API version:  1.26 (minimum version 1.12)
 Go version:   go1.7.5
 Git commit:   092cba3
 Built:        Wed Feb  8 08:47:51 2017
 OS/Arch:      linux/amd64
 Experimental: false
███  DOCKER COMPOSE
Docker Compose: docker-compose version 1.11.1, build 7afaa436
docker-py version: 2.0.2
CPython version: 2.7.13
OpenSSL version: OpenSSL 1.0.2j  26 Sep 2016
███  DOCKER MACHINE
docker-machine.exe version 0.9.0, build 15fd4c7
time="2017-04-05T15:57:21+03:00" level=info msg="Unable to use system certificate pool: crypto/x509:                                                                                                                                          system root pool is not available on Windows"
███  DOCKER: IMAGES
time="2017-04-05T15:57:21+03:00" level=info msg="Unable to use system certificate pool: crypto/x509:                                                                                                                                          system root pool is not available on Windows"
REPOSITORY            TAG                 IMAGE ID            CREATED             SIZE
docksal/vhost-proxy   1.0                 2c8a8b1e62c4        4 weeks ago         164 MB
docksal/dns           1.0                 20c7a535479d        2 months ago        61.6 MB
docksal/ssh-agent     1.0                 148220cc033d        2 months ago        12.2 MB
███  DOCKER: CONTAINERS
time="2017-04-05T15:57:21+03:00" level=info msg="Unable to use system certificate pool: crypto/x509:                                                                                                                                          system root pool is not available on Windows"
CONTAINER ID        IMAGE                     COMMAND                  CREATED             STATUS                                                                                                                                                       PORTS                                      NAMES
8cfe9a3e698c        docksal/ssh-agent:1.0     "/run.sh ssh-agent"      4 minutes ago       Up 4 minu                                                                                                                                         tes                                                   docksal-ssh-agent
c0af953507e8        docksal/dns:1.0           "/opt/entrypoint.s..."   4 minutes ago       Up 4 minu                                                                                                                                         tes        192.168.64.100:53->53/udp                  docksal-dns
b187e5b0eb5f        docksal/vhost-proxy:1.0   "/usr/local/bin/st..."   4 minutes ago       Up 4 minu                                                                                                                                         tes        0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp   docksal-vhost-proxy
███  VIRTUALBOX
5.1.14r112924
███  NETWORK INTERFACES
Name:            VirtualBox Host-Only Ethernet Adapter #2
GUID:            5334936f-030d-4566-9537-257d99299646
DHCP:            Disabled
IPAddress:       192.168.64.1
NetworkMask:     255.255.255.0
IPV6Address:     fe80:0000:0000:0000:8087:12cf:3db8:353c
IPV6NetworkMaskPrefixLength: 64
HardwareAddress: 0a:00:27:00:00:14
MediumType:      Ethernet
Status:          Up
VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #2

███  MOUNTS
tmpfs on / type tmpfs (rw,relatime,size=917696k)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
devpts on /dev/pts type devpts (rw,relatime,mode=600,ptmxmode=000)
tmpfs on /dev/shm type tmpfs (rw,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
/dev/sda1 on /mnt/sda1 type ext4 (rw,relatime,data=ordered)
cgroup on /sys/fs/cgroup type tmpfs (rw,relatime,mode=755)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,relatime,cpuset)
cgroup on /sys/fs/cgroup/cpu type cgroup (rw,relatime,cpu)
cgroup on /sys/fs/cgroup/cpuacct type cgroup (rw,relatime,cpuacct)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,relatime,blkio)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,relatime,memory)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,relatime,net_cls)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,relatime,perf_event)
cgroup on /sys/fs/cgroup/net_prio type cgroup (rw,relatime,net_prio)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,relatime,hugetlb)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,relatime,pids)
/dev/sda1 on /mnt/sda1/var/lib/docker/aufs type ext4 (rw,relatime,data=ordered)
none on /mnt/sda1/var/lib/docker/aufs/mnt/54bfab079a51fbd2a898fefb564e7673145afbb1f7a81117df37a653b2                                                                                                                                         578281 type aufs (rw,relatime,si=23b8904b979734f0,dio,dirperm1)
shm on /mnt/sda1/var/lib/docker/containers/b187e5b0eb5f226e8ff208af46374f510d18f22f2fb9eb540c6229c52                                                                                                                                         3d81a4c/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=65536k)
nsfs on /var/run/docker/netns/a0a2b8454f82 type nsfs (rw)
none on /mnt/sda1/var/lib/docker/aufs/mnt/e96979054b4735a7e7af0e22b567f245455bfabf27e6d5307108439c1f                                                                                                                                         d56834 type aufs (rw,relatime,si=23b8904b818644f0,dio,dirperm1)
shm on /mnt/sda1/var/lib/docker/containers/c0af953507e8a6104152fc0394d3fb3db921d13e4c70c6037b12bd544                                                                                                                                         6fda456/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=65536k)
nsfs on /var/run/docker/netns/a1a73c6f69be type nsfs (rw)
none on /mnt/sda1/var/lib/docker/aufs/mnt/1e13c2d23a7e16f046b56994b3f5c3bee31d058e788d0c07f3e65704a6                                                                                                                                         c14988 type aufs (rw,relatime,si=23b8904b80b1d4f0,dio,dirperm1)
shm on /mnt/sda1/var/lib/docker/containers/8cfe9a3e698c08553e7ebf03ed073d277959be3a0166d21c61774686c                                                                                                                                         9b25a1b/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=65536k)
nsfs on /var/run/docker/netns/d5ee54877ac8 type nsfs (rw)
vaza18 picture vaza18 on 5 Apr 2017

@vaza18

mount: mounting //192.168.64.1/c on /c failed: Key has expired

According to this - can you try changing the Windows user password and see if that helps?

lmakarov picture lmakarov on 5 Apr 2017

@lmakarov as per @vaza18 comments in chat password changing is disabled by domain policies.

achekulaev picture achekulaev on 5 Apr 2017 
C:\Users\name.second_name>net user name.second_name
Имя пользователя                       name.second_name
Полное имя                             Name
Комментарий
Комментарий пользователя
Код страны или региона                 000 (Стандартный системный)
Учетная запись активна                 No
Учетная запись просрочена              Никогда
Последний пароль задан                 3/20/2015 4:25:03 PM
Действие пароля завершается            Никогда
Пароль допускает изменение             3/21/2015 4:25:03 PM
Требуется пароль                       Yes
Пользователь может изменить пароль     Yes
Разрешенные рабочие станции            Все
Сценарий входа
Конфигурация пользователя
Основной каталог
Последний вход                         Никогда
Разрешенные часы входа                 Все
Членство в локальных группах           *Пользователи
Членство в глобальных группах          *None
Команда выполнена успешно.

C:\Users\name.second_name>

C:\Users\name.second_name>net user name.second_name DOMAINNAME
Системная ошибка 5.
Отказано в доступе.
vaza18 picture vaza18 on 6 Apr 2017

Учетная запись активна No

Account is disabled. I don't know why user is able to log in @vaza18
Could user check with domain admins on this matter?

achekulaev picture achekulaev on 6 Apr 2017

No updates. Closing.

achekulaev picture achekulaev on 24 Apr 2017

Had the same issue and resolved it by typing the Microsoft account password, instead of the one that I use to unlock my PC!!! When you use the Microsoft account, you can set up a different password to unlock your PC (like a shorter password for convenience), and that is what I had set up!

dimaboychev picture dimaboychev on 28 Apr 2017
👍1

@dimaboychev Thanks for sharing this and glad it worked for you. Do you have a standalone Windows box or is it connected to a Windows domain?

I've been helping someone installing Docksal on a Windows 8 machine today and ran into this same problem. It was a corporate machine (joined to a Windows domain).
The domain username/password would not work (worth noting that the domain was not available at the time this was done).
We ended up creating a local user account, updating the share and file system permissions to give access to that user, then hardcoding that user name in fin. It's a dirty setup, but it eventually worked.

lmakarov picture lmakarov on 28 Apr 2017

@lmakarov standalone windows 10

PS
Awesome presentation at DrupalCon :)

dimaboychev picture dimaboychev on 28 Apr 2017

I have this issue as well. I'm on Windows 10 and I'm connected to a Windows domain. I've tried the password for the account I'm logged in to, one for a local admin account, and as the previous suggestion explains, one for my Microsoft account (which I actually had to add by going to the "Your email and accounts" settings page).
Nothing has worked so far, I continually get:

Enter your Windows account password:
mount: mounting //192.168.64.1/c on /c failed: Permission denied
exit status 255
Error creating share

:(

jmdodge picture jmdodge on 3 May 2017

@jmdodge so the domain password doesn't work for you while the domain is available at the time you're trying to do this? Worth noting that my machine is not connected to a domain and I already had Microsoft account connected long before trying docksal.

dimaboychev picture dimaboychev on 3 May 2017

@dimaboychev - that is correct, the domain is available but the password doesn't work. While the domain is available, I had tried the password for my current user on the domain, an admin account password, and my Microsoft password for an account I added afterwards.

I have made a little progress though - I tried setting up a new local windows user which was tied to my Microsoft account (so note: the password I use to log in with is the same as the password for my Microsoft account).

Permission problems with local accounts too!
Initially I had the exact same problem with my local account, but after some digging I found the solution here: https://cdn-enterprise.discourse.org/docker/uploads/default/optimized/2X/0/06c4954581641408a5bbf7b1a1a01e2dbba82f03_1_685x500.jpg
(comes from the following issue: https://forums.docker.com/t/volume-mounts-in-windows-does-not-work/10693/115).
So it sounds like some upgraded instructions are in order (or maybe this can be done via installer?)

This describes adding a "Users" user to the windows sharing permissions for the volume I'm trying to mount and giving it permissions to the drive. Now, I can get the mount going for my _local_ account. I went back to my _domain_ account thinking that this might have solved it retroactively, but no dice - I cannot get it working for the domain user.

Files in mount are world writable
Now a new problem: inside the container, everything in the mount seems to be world writable, and this causes the site install to fail due to a mysql problem. The whole issue is a bit of a catch 22:

  1. Warning: World-writable config file '/etc/mysql/my.cnf' is ignored
  2. Tried to chmod, but I can't use sudo chmod because: 
sudo: error in /etc/sudo.conf, line 0 while loading plugin `sudoers_policy'
sudo: /usr/lib/sudo/sudoers.so must be only be writable by owner
sudo: fatal error, unable to load plugins
  1. Can't su: su: must be run from a terminal

Update: I was able to get the site to install by renaming the old my.cnf and creating a new one. The new file is owned by the 'docker' user and has acceptable permissions. Currently I left the file blank and I that seems to be good enough, but without any sudo powers the environment is relatively crippled, and doubtless there will be other problems with world writable permissions (using ssh keys for example).

Any advice?

jmdodge picture jmdodge on 4 May 2017

Ok Now I think I see the issue. Looks like many of you guys had pre-existing shares for your local drives which effectively means this one https://github.com/docksal/docksal/issues/165 that is in the queue.

I guess we will need to prioritize that one.

In the meantime I would advice to:
1) fin vm stop
2) delete pre-existing shares for your local drives \\computer\c, \\computer\d etc.
3) fin vm start should create properly made shares

achekulaev picture achekulaev on 4 May 2017

@achekulaev - I'm glad all this could help lead to a clarification. I did not follow the instructions you just posted, but when I created a new Docksal project after having previously resolved the permissions for my pre-existing share, the new project seems to have appropriate file permissions and I have an environment that now seems to be running smoothly.

The project with my world-writable file issues still has the issue even after restarting the vm several times and trying a 'fin reset'. I presume that if I kept poking it I could resolve the issue, but it was just a test project so I'm moving on.

Thanks! I hope the setup process for us poor windows users can be improved, overall several different issues have made it a minor nightmare to get going - but I'm enjoying it now!

jmdodge picture jmdodge on 4 May 2017

Thanks @jmdodge
And yes, we are going to dedicate the next sprint to the world beloved operating system Windows and to the issues that users meet there with Docksal :)

achekulaev picture achekulaev on 4 May 2017

p.s. If you could create a separate issue about my.cnf and describe how to reproduce it, we could look at it as well.

achekulaev picture achekulaev on 4 May 2017

@achekulaev : Thank you for your remediation suggestion. How do we delete pre-existing shares?
Thanks again!

unknownterritory picture unknownterritory on 4 May 2017

@unknownterritory https://youtu.be/yN9FKHWbW48?t=1m7s

achekulaev picture achekulaev on 4 May 2017

@achekulaev , was expecting something more complex, lol.
Thanks again!

unknownterritory picture unknownterritory on 4 May 2017

For those that prefer the command line, this page contains the necessary information. Basically, you open a command line with administrator privileges and issue the command:
net share <sharename> /delete
In Docksal's case that would be:
net share c /delete
repeated to any other drives you might have shared with Docksal's vm.

unknownterritory picture unknownterritory on 4 May 2017

@lmakarov maybe we can try smbfs instead of cifs
sudo mount -t smbfs ...
Looks like there is dozen of options to mount a folder and they might depend on AD setup too https://serverfault.com/questions/508573/mount-error13-permission-denied-with-windows-share

achekulaev picture achekulaev on 5 May 2017

I am on Windows 7 and I am also unable to mount the drive although I can see that the drive does become mounted right at that point of the script. Here is the error I get same as the others:

Enter your Windows account password:
Adding docker SMB share...
mount: mounting //192.168.64.1/c on /c failed: Permission denied
exit status 255
Error creating share
Could not start Docksal docker machine properly

I have tried all of the passwords I can think of and am not sure how to create a new password for a "Microsoft account" if the password is actually the issue.

drubage picture drubage on 5 May 2017

Thanks for reporting @drubage
Could you try the workaround from https://github.com/docksal/docksal/issues/117#issuecomment-299246650 (Giving a group "Users" full access to your \\computer\c, \\computer\d shares) and tell if it solves the issue for you?

achekulaev picture achekulaev on 5 May 2017

I did give Users full access to C for sharing. I then removed the share it created from the prior "fin vm start" and tried again and still get the same error. If I look at my C: properties under sharing I see that a share was added to \DRFRULPT-PC\c but docker is not liking it for some reason.

drubage picture drubage on 5 May 2017

@drubage got it, thanks so much for trying and reporting back.

Looks like on some Windows installations we need to try other security options when mounting a folder.

I will create those test fin versions and post here an update how to try them out. Stay tuned!

achekulaev picture achekulaev on 5 May 2017

@drubage I've created an alpha version of fin that allows to experiment with security options.

Could you please download that version with this command

DOCKSAL_VERSION=alpha fin update --self

Then export an alternative NTLM security option like this:

export NTLM="ntlmssp"

And then try restarting your VM with fin vm restart again.

During folder mounting, after entering password you should see a message that NTLM is using alternative security option. Please let know if it helps with your issue.

achekulaev picture achekulaev on 5 May 2017

Ok it was able to start the VM and I was able to do a fin init in the drupal8 project folder (cloned from https://github.com/docksal/drupal8) but I get the following error (although this might be an error related to that repo and not Docksal but I will post here just in case):

The website encountered an unexpected error. Please try again later.

Drupal\Component\Plugin\Exception\PluginNotFoundException: The "image" plugin does not exist. in Drupal\Core\Plugin\DefaultPluginManager->doGetDefinition() (line 52 of core/lib/Drupal/Component/Plugin/Discovery/DiscoveryTrait.php).
Drupal\Core\Plugin\DefaultPluginManager->getDefinition('image') (Line: 56)
Drupal\Core\Field\FormatterPluginManager->createInstance('image', Array) (Line: 126)
Drupal\Core\Field\FormatterPluginManager->getInstance(Array) (Line: 201)
Drupal\Core\Entity\Entity\EntityViewDisplay->getRenderer('user_picture') (Line: 232)
Drupal\Core\Entity\Entity\EntityViewDisplay->buildMultiple(Array) (Line: 303)
Drupal\Core\Entity\EntityViewBuilder->buildComponents(Array, Array, Array, 'full') (Line: 246)
Drupal\Core\Entity\EntityViewBuilder->buildMultiple(Array) (Line: 203)
Drupal\Core\Entity\EntityViewBuilder->build(Array)
call_user_func(Array, Array) (Line: 376)
Drupal\Core\Render\Renderer->doRender(Array, ) (Line: 195)
Drupal\Core\Render\Renderer->render(Array, ) (Line: 226)
Drupal\Core\Render\MainContent\HtmlRenderer->Drupal\Core\Render\MainContent\{closure}() (Line: 574)
Drupal\Core\Render\Renderer->executeInRenderContext(Object, Object) (Line: 227)
Drupal\Core\Render\MainContent\HtmlRenderer->prepare(Array, Object, Object) (Line: 117)
Drupal\Core\Render\MainContent\HtmlRenderer->renderResponse(Array, Object, Object) (Line: 90)
Drupal\Core\EventSubscriber\MainContentViewSubscriber->onViewRenderArray(Object, 'kernel.view', Object) (Line: 111)
Drupal\Component\EventDispatcher\ContainerAwareEventDispatcher->dispatch('kernel.view', Object) (Line: 144)
Symfony\Component\HttpKernel\HttpKernel->handleRaw(Object, 1) (Line: 62)
Symfony\Component\HttpKernel\HttpKernel->handle(Object, 1, 1) (Line: 57)
Drupal\Core\StackMiddleware\Session->handle(Object, 1, 1) (Line: 47)
Drupal\Core\StackMiddleware\KernelPreHandle->handle(Object, 1, 1) (Line: 47)
Drupal\Core\StackMiddleware\ReverseProxyMiddleware->handle(Object, 1, 1) (Line: 50)
Drupal\Core\StackMiddleware\NegotiationMiddleware->handle(Object, 1, 1) (Line: 23)
Stack\StackedHttpKernel->handle(Object, 1, 1) (Line: 652)
Drupal\Core\DrupalKernel->handle(Object) (Line: 19)
drubage picture drubage on 5 May 2017

@drubage great news! Thanks so much for your help.

It looks like a generic Drupal error and I don't think it's related to Docksal. To double check you can go to your projects folder and use fin project create to create dest Drupal 8 site. If you have issues with that installation please definitely let know. However if that site works fine then it's error related to your drupal repo.

achekulaev picture achekulaev on 5 May 2017

@drubage can you post full output of fin vm start? Looks like the mount error is gone now? :)

Also, just to confirm the mount actually happened, please run this and post the output:

fin docker-machine ssh docksal 'mount | grep 192.168.64.1'
lmakarov picture lmakarov on 5 May 2017

Starting a Drupal 8 project with fin project create worked well. I thought we could clone that repository also as a starting point but I see now how to start a project from scratch. The folder is mapped as I can make updates in my windows files and see the updates in real time in the virtual machine. Pretty awesome!

Here is the output of fin docker-machine ssh docksal 'mount | grep 192.168.64.1':

//192.168.64.1/c on /c type cifs (rw,relatime,vers=1.0,sec=ntlmssp,cache=strict,username=drew.michael,domain=FRUITION,uid=0,noforceuid,gid=0,noforcegid,addr=192.168.64.1,file_mode=0777,dir_mode=0777,nounix,serverino,mapposix,nobrl,mfsymlinks,noperm,rsize=61440,wsize=65536,actimeo=1)
//192.168.64.1/c on /mnt/sda1/var/lib/docker/volumes/drupal8_host_home/_data type cifs (rw,relatime,vers=1.0,sec=ntlmssp,cache=strict,username=drew.michael,domain=FRUITION,uid=0,noforceuid,gid=0,noforcegid,addr=192.168.64.1,file_mode=0777,dir_mode=0777,nounix,serverino,mapposix,nobrl,mfsymlinks,noperm,rsize=61440,wsize=65536,actimeo=1)
//192.168.64.1/c on /mnt/sda1/var/lib/docker/volumes/drupal8_project_root/_data type cifs (rw,relatime,vers=1.0,sec=ntlmssp,cache=strict,username=drew.michael,domain=FRUITION,uid=0,noforceuid,gid=0,noforcegid,addr=192.168.64.1,file_mode=0777,dir_mode=0777,nounix,serverino,mapposix,nobrl,mfsymlinks,noperm,rsize=61440,wsize=65536,actimeo=1)
//192.168.64.1/c on /mnt/sda1/var/lib/docker/volumes/drupal8test_host_home/_data type cifs (rw,relatime,vers=1.0,sec=ntlmssp,cache=strict,username=drew.michael,domain=FRUITION,uid=0,noforceuid,gid=0,noforcegid,addr=192.168.64.1,file_mode=0777,dir_mode=0777,nounix,serverino,mapposix,nobrl,mfsymlinks,noperm,rsize=61440,wsize=65536,actimeo=1)
//192.168.64.1/c on /mnt/sda1/var/lib/docker/volumes/drupal8test_project_root/_data type cifs (rw,relatime,vers=1.0,sec=ntlmssp,cache=strict,username=drew.michael,domain=FRUITION,uid=0,noforceuid,gid=0,noforcegid,addr=192.168.64.1,file_mode=0777,dir_mode=0777,nounix,serverino,mapposix,nobrl,mfsymlinks,noperm,rsize=61440,wsize=65536,actimeo=1)
drubage picture drubage on 5 May 2017

Ok we're fixing it in fin and it will be in release soon. As you see there's already a commit that closes this issue. Hopefully we don't have to re-open it

achekulaev picture achekulaev on 5 May 2017

Just a follow-up here that might be relevant I am not sure. If I do a git pull in the VM to pull in a new project I need to make the files not be read-only. In Windows I right click on the new project folder and click "properties" and the under the "attributes" section "Read Only (Only applies to files in folder)" is like partially checked so I uncheck the box and click "apply". Only then can I successfully run commands like drush make. If I don't do that then the system cannot seem to find or read the file but after doing that everything seems to work okay.

drubage picture drubage on 9 May 2017

We have just pushed a new release v1.3.0 with the improvements for Windows SMB sharing. We encourage everyone here to update and try it out. Especially we are looking for the feedback from Windows users in corporate/domain environments.

lmakarov picture lmakarov on 16 May 2017

@lmakarov - apologies for my ignorance here and that this may not be the best place to ask the question, but I am a little unclear on how to update.
I tried fin update, but fin reports its version as 1.9.0 before and after the update. I have been using Drupal 7 sample project as a start point, but that repo does not appear to have been updated for a while.
Which thing do I update and how?

jmdodge picture jmdodge on 17 May 2017

@jmdodge http://docs.docksal.io/en/master/getting-started/setup/#updates

fin update is all you have to run to update all Docksal components and dependencies.

There is no way to check the version of Docksal that you currently have. You can determine it by the version of fin. Docksal version 1.3.0 is the latest and fin version 1.9.0 is the latest (part of the 1.3.0 Docksal release).

We will be adding this information in the release notes and updates the docs to avoid the confusion for new users.

lmakarov picture lmakarov on 17 May 2017

I have done a successful update, but I'm afraid that since updating the mounting process seem to be fairly broken. When I try to restart the vm:

{ ~ }  » fin vm restart                                                                                                                                ~ 1
Stopping "docksal"...
Machine "docksal" was stopped.
Starting "docksal"...
(docksal) Check network to re-create if needed...
(docksal) Waiting for an IP...
Machine "docksal" was started.
Waiting for SSH to be available...
Detecting the provisioner...
Started machines may have new IP addresses. You may need to re-run the `docker-machine env` command.
Configuring SMB shares...
Enter your Windows account password:
exit status 255
Mount command failed... Trying an alternative method...
exit status 255
 ERROR:  SMB share mount failed.
         Make sure your Windows password is correct and run fin vm restart to try again.

I also tried running fin vm remove and then fin vm start, but it didn't help.

Output of fin sysinfo:


fin sysinfo output

```
███ OS & BASICS
CYGWIN_NT-10.0-WOW REM-LT-30 2.8.0(0.309/5/3) 2017-04-01 20:42 i686 Cygwin
Microsoft Windows [Version 10.0.10586]
fin version: 1.9.0
Mode: VirtualBox VM
███ INSTANCES
NAME ACTIVE DRIVER STATE URL SWARM DOCKER ERRORS
docksal * virtualbox Running tcp://192.168.64.100:2376 v17.04.0-ce
███ DOCKER
DOCKER_HOST: tcp://192.168.64.100:2376

Docker: Client:
Version: 17.04.0-ce
API version: 1.28
Go version: go1.7.5
Git commit: 4845c56
Built: Wed Apr 5 23:33:17 2017
OS/Arch: windows/amd64

Server:
Version: 17.04.0-ce
API version: 1.28 (minimum version 1.12)
Go version: go1.7.5
Git commit: 4845c56
Built: Wed Apr 5 18:45:47 2017
OS/Arch: linux/amd64
Experimental: false
███ DOCKER COMPOSE
Docker Compose: docker-compose version 1.12.0, build ee0f34e1
docker-py version: 2.2.1
CPython version: 2.7.13
OpenSSL version: OpenSSL 1.0.2j 26 Sep 2016
███ DOCKER MACHINE
docker-machine.exe version 0.10.0, build 76ed2a6
███ DOCKER: IMAGES
REPOSITORY TAG IMAGE ID CREATED SIZE
docksal/vhost-proxy 1.0 2c8a8b1e62c4 2 months ago 164MB
docksal/dns 1.0 20c7a535479d 3 months ago 61.6MB
docksal/ssh-agent 1.0 148220cc033d 3 months ago 12.2MB
███ DOCKER: CONTAINERS
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
b3d5d9e0818c docksal/ssh-agent:1.0 "/run.sh ssh-agent" 36 minutes ago Up About a minute docksal-ssh-agent
d24f002ae278 docksal/dns:1.0 "/opt/entrypoint.s..." 36 minutes ago Up About a minute 192.168.64.100:53->53/udp docksal-dns
466a4e7f76ea docksal/vhost-proxy:1.0 "/usr/local/bin/st..." 36 minutes ago Up About a minute 192.168.64.100:80->80/tcp, 192.168.64.100:443->443/tcp docksal-vhost-proxy
███ VIRTUALBOX
5.1.18r114002
███ NETWORK INTERFACES
Name: VirtualBox Host-Only Ethernet Adapter #6
GUID: af04fab4-0eee-42e4-8344-73b741cfcc56
DHCP: Disabled
IPAddress: 192.168.64.1
NetworkMask: 255.255.255.0
IPV6Address: fe80:0000:0000:0000:1c0d:ca52:354a:7cee
IPV6NetworkMaskPrefixLength: 64
HardwareAddress: 0a:00:27:00:00:13
MediumType: Ethernet
Status: Up
VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #6

███ MOUNTS
tmpfs on / type tmpfs (rw,relatime,size=917692k)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
devpts on /dev/pts type devpts (rw,relatime,mode=600,ptmxmode=000)
tmpfs on /dev/shm type tmpfs (rw,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
/dev/sda1 on /mnt/sda1 type ext4 (rw,relatime,data=ordered)
cgroup on /sys/fs/cgroup type tmpfs (rw,relatime,mode=755)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,relatime,cpuset)
cgroup on /sys/fs/cgroup/cpu type cgroup (rw,relatime,cpu)
cgroup on /sys/fs/cgroup/cpuacct type cgroup (rw,relatime,cpuacct)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,relatime,blkio)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,relatime,memory)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,relatime,net_cls)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,relatime,perf_event)
cgroup on /sys/fs/cgroup/net_prio type cgroup (rw,relatime,net_prio)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,relatime,hugetlb)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,relatime,pids)
/dev/sda1 on /mnt/sda1/var/lib/docker/aufs type ext4 (rw,relatime,data=ordered)
none on /mnt/sda1/var/lib/docker/aufs/mnt/68c0cb8d1f2747c77d13098a7221f8da186c4c111603c880f051bbd0d685669b type aufs (rw,relatime,si=b9f882adbcbc5a2d,dio,dirperm1)
none on /mnt/sda1/var/lib/docker/aufs/mnt/2f33f8059e9310ca8928fdfaf03e3fa9cc015a0138349fd8bf1ea27a45a3fabf type aufs (rw,relatime,si=b9f882adbc4b0a2d,dio,dirperm1)
none on /mnt/sda1/var/lib/docker/aufs/mnt/20a1b772d14f6fa0c86c1eb62912c5be3c5eca086f7a3061790f032e21afb50f type aufs (rw,relatime,si=b9f882adbcae8a2d,dio,dirperm1)
shm on /mnt/sda1/var/lib/docker/containers/d24f002ae278e2636e916fc10da5136ce5b7bd157422d445dae91ee2b08ff178/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=65536k)
shm on /mnt/sda1/var/lib/docker/containers/b3d5d9e0818c8948324c2c0e7fab5d18ddc600d4edcca0220c3bee86628b467d/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=65536k)
shm on /mnt/sda1/var/lib/docker/containers/466a4e7f76ea11081539913c777bc27119e2208e9b87cf0fcfb85c20b9233732/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=65536k)
nsfs on /var/run/docker/netns/95f5e1d3b07f type nsfs (rw)
nsfs on /var/run/docker/netns/f64ad93faab8 type nsfs (rw)
nsfs on /var/run/docker/netns/a673d6743bae type nsfs (rw)

```

jmdodge picture jmdodge on 18 May 2017

@jmdodge jeez I'm really sorry it's broken! :(
So was it working fine before for you, but now it's broken?

achekulaev picture achekulaev on 18 May 2017

@jmdodge

I'm afraid that since updating the mounting process seem to be fairly broken

Try using you local/domain user password, not the Microsoft one.

Also, Docksal is now creating shares like docksal-c instead of just c to avoid possible overlaps with existing shares. There is nothing you should do about that, JFYI.

$ net share

Share name   Resource                        Remark

-------------------------------------------------------------------------------
C$           C:\                             Default share
IPC$                                         Remote IPC
ADMIN$       C:\Windows                      Remote Admin
docksal-c    C:\                             Docksal C: drive
The command completed successfully.
lmakarov picture lmakarov on 18 May 2017

@jmdodge I've been helping someone internally with a similar issue today. In that case the problem was with Windows not giving access to the share ONLY on the VirtualBox interface IP address.

Try opening \\192.168.64.1\ in Explorer (the file browser) - http://take.ms/oaMXw
If that does not work, try changing the IP to your LAN IP.

Update: \\192.168.64.1, not \\192.168.64.100

lmakarov picture lmakarov on 18 May 2017

Troubleshooting SMB share creation, share mounting and related issues on Windows guide
It is a work in progress, so may contain mistakes.

achekulaev picture achekulaev on 26 May 2017

I have followed the guide and I can see that the share is being created just fine and all steps work so I'm back to submitting a new issue but I am not sure if you want me to do that or if you want me to wait until you overcome this new windows issue or want more information from me?

drubage picture drubage on 30 May 2017

@drubage I thought you were good. Did your setup stop working?

What's the output from fin vm mount?

lmakarov picture lmakarov on 30 May 2017

Please see #233 for the ticket I had created. I am getting a different error now of:

error during connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.28/info: open //./pipe/docker_engine: The system cannot find the file specified. In the default daemon configuration on Windows, the docker client must be run elevated to connect. This error may also indicate that the docker daemon is not running.

Output of fin vm mount:

drfrulpt-PC% fin vm mount
Configuring SMB shares...
Enter your Windows account password:
drubage picture drubage on 30 May 2017

@drubage the last error you posted is not directly related to mounting shares on Windows.

When do you get this error? Please post fin sysinfo again.

lmakarov picture lmakarov on 31 May 2017

I get the error trying to fin up a project. Here is fin sysinfo:

drfrulpt-PC% fin sysinfo
███  OS & BASICS
CYGWIN_NT-6.1-WOW drfrulpt-PC 1.7.35(0.287/5/3) 2015-03-04 12:07 i686 Cygwin
 Microsoft Windows [Version 6.1.7601]
fin version: 1.9.0
Mode:  VirtualBox VM
███  INSTANCES
NAME      ACTIVE   DRIVER       STATE     URL                         SWARM   DOCKER        ERRORS
default   -        virtualbox   Error                                         Unknown       machine    does not exist
docksal   -        virtualbox   Running   tcp://192.168.64.100:2376           v17.04.0-ce
███  DOCKER
DOCKER_HOST:

error during connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.28/version: open //./pipe/docker_   engine: The system cannot find the file specified. In the default daemon configuration on Windows, t   he docker client must be run elevated to connect. This error may also indicate that the docker daemo   n is not running.
Docker: Client:
 Version:      17.04.0-ce
 API version:  1.28
 Go version:   go1.7.5
 Git commit:   4845c56
 Built:        Wed Apr  5 23:33:17 2017
 OS/Arch:      windows/amd64
███  DOCKER COMPOSE
Docker Compose: docker-compose version 1.12.0, build ee0f34e1
docker-py version: 2.2.1
CPython version: 2.7.13
OpenSSL version: OpenSSL 1.0.2j  26 Sep 2016
███  DOCKER MACHINE
docker-machine.exe version 0.10.0, build 76ed2a6
error during connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.28/info: open //./pipe/docker_eng   ine: The system cannot find the file specified. In the default daemon configuration on Windows, the    docker client must be run elevated to connect. This error may also indicate that the docker daemon i   s not running.
███  VIRTUALBOX
5.1.22r115126
███  NETWORK INTERFACES
Name:            VirtualBox Host-Only Ethernet Adapter #3
GUID:            e6454998-e50d-4b68-bd21-c418e0bf868b
DHCP:            Disabled
IPAddress:       192.168.64.1
NetworkMask:     255.255.255.0
IPV6Address:     fe80:0000:0000:0000:0dde:b532:700f:bdb3
IPV6NetworkMaskPrefixLength: 64
HardwareAddress: 0a:00:27:00:00:39
MediumType:      Ethernet
Status:          Up
VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #3

Name:            VirtualBox Host-Only Ethernet Adapter #5
GUID:            04a45e75-8f4f-43d5-b64a-39cfefe14441
DHCP:            Enabled
IPAddress:       169.254.77.44
NetworkMask:     255.255.0.0
IPV6Address:     fe80:0000:0000:0000:c90e:e29e:6baa:4d2c
IPV6NetworkMaskPrefixLength: 64
HardwareAddress: 0a:00:27:00:00:33
MediumType:      Ethernet
Status:          Up
VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #5

Name:            VirtualBox Host-Only Ethernet Adapter #4
GUID:            055ec56b-bdd7-4a00-95d2-1d2e3e751213
DHCP:            Enabled
IPAddress:       169.254.13.97
NetworkMask:     255.255.0.0
IPV6Address:     fe80:0000:0000:0000:f939:c842:e9bf:0d61
IPV6NetworkMaskPrefixLength: 64
HardwareAddress: 0a:00:27:00:00:31
MediumType:      Ethernet
Status:          Up
VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #4

Name:            VirtualBox Host-Only Ethernet Adapter #2
GUID:            a57ef571-f08d-40fe-9967-a9ed529a803b
DHCP:            Disabled
IPAddress:       192.168.88.1
NetworkMask:     255.255.255.0
IPV6Address:     fe80:0000:0000:0000:6cd6:90a4:3165:db81
IPV6NetworkMaskPrefixLength: 64
HardwareAddress: 0a:00:27:00:00:1b
MediumType:      Ethernet
Status:          Up
VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #2

Name:            VirtualBox Host-Only Ethernet Adapter
GUID:            58be5bf6-a111-43be-9723-1da59beb5683
DHCP:            Disabled
IPAddress:       192.168.56.1
NetworkMask:     255.255.255.0
IPV6Address:     fe80:0000:0000:0000:6c34:cc99:0894:a7c0
IPV6NetworkMaskPrefixLength: 64
HardwareAddress: 0a:00:27:00:00:10
MediumType:      Ethernet
Status:          Up
VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter

███  MOUNTS
tmpfs on / type tmpfs (rw,relatime,size=917692k)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
devpts on /dev/pts type devpts (rw,relatime,mode=600,ptmxmode=000)
tmpfs on /dev/shm type tmpfs (rw,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
/dev/sda1 on /mnt/sda1 type ext4 (rw,relatime,data=ordered)
cgroup on /sys/fs/cgroup type tmpfs (rw,relatime,mode=755)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,relatime,cpuset)
cgroup on /sys/fs/cgroup/cpu type cgroup (rw,relatime,cpu)
cgroup on /sys/fs/cgroup/cpuacct type cgroup (rw,relatime,cpuacct)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,relatime,blkio)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,relatime,memory)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,relatime,net_cls)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,relatime,perf_event)
cgroup on /sys/fs/cgroup/net_prio type cgroup (rw,relatime,net_prio)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,relatime,hugetlb)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,relatime,pids)
/dev/sda1 on /mnt/sda1/var/lib/docker/aufs type ext4 (rw,relatime,data=ordered)
none on /mnt/sda1/var/lib/docker/aufs/mnt/922345e093082a416ca2db3b53870b591bcc4118b206675b0de27ffa1f   6aabd2 type aufs (rw,relatime,si=5281772e65fe2ff,dio,dirperm1)
shm on /mnt/sda1/var/lib/docker/containers/b325362fa8a62544d3dec2df87764d77ef99d33a019b6941da7d36730   d6ef131/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=65536k)
none on /mnt/sda1/var/lib/docker/aufs/mnt/7b8b7944ed4891c7dbf18807b116c1fbbc425695e09a23907f7e18923e   3a96ba type aufs (rw,relatime,si=5281772e86e72ff,dio,dirperm1)
shm on /mnt/sda1/var/lib/docker/containers/f9bbd4e20cee5e403edd8c20545bf14af15e8f0e6547f733f37f1185e   6b92309/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=65536k)
none on /mnt/sda1/var/lib/docker/aufs/mnt/8507e3a1b11ba99260d04760d370591a3ea8ea27ccc3e6e6fd9f94a43a   58ba37 type aufs (rw,relatime,si=5281772e88842ff,dio,dirperm1)
shm on /mnt/sda1/var/lib/docker/containers/7baf7cf50807ba2e128bbcc5e3e1553a11d87050eb41ef54918ac3e5a   b5ac35d/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=65536k)
nsfs on /var/run/docker/netns/77a193823144 type nsfs (rw)
nsfs on /var/run/docker/netns/dc7a636922c4 type nsfs (rw)
nsfs on /var/run/docker/netns/5f41c66ffe36 type nsfs (rw)
//192.168.64.1/docksal-c on /c type cifs (rw,relatime,vers=1.0,sec=ntlmssp,cache=strict,username=dre   w.michael,domain=FRUITION,uid=0,noforceuid,gid=0,noforcegid,addr=192.168.64.1,file_mode=0777,dir_mod   e=0777,nounix,serverino,mapposix,nobrl,mfsymlinks,noperm,rsize=61440,wsize=65536,actimeo=1)
drubage picture drubage on 31 May 2017

@drubage ok, so the last line there tells that the share and mount is good

...
//192.168.64.1/docksal-c on /c type cifs (rw,relatime,vers=1.0,sec=ntlmssp,cache=strict,username=dre   w.michael,domain=FRUITION,uid=0,noforceuid,gid=0,noforcegid,addr=192.168.64.1,file_mode=0777,dir_mod   e=0777,nounix,serverino,mapposix,nobrl,mfsymlinks,noperm,rsize=61440,wsize=65536,actimeo=1)

Please create a separate issue following the issue template and let's move further discussions there.
I'll post several steps to try there as soon as I see the issue created.

lmakarov picture lmakarov on 31 May 2017

@drubage hi! Thanks for reporting. Don't mean to bounce you around, but looks like mounting issue is fixed for you. The issue you're getting now is very generic "can not reach docker daemon" issue. We'd like to have that discussion separate from mounting issues. Thanks for keeping reporting issues. We really need that as we can't reproduce all those edge cases on our own.

achekulaev picture achekulaev on 31 May 2017

I've updated Docksal (fin v1.10.0) and continue to have the mounting share issues in my windows 10. To be clear, shares are created correctly the first time... Then, when my computer sleeps and then resumes, or when I reboot it, and I have to to a fin vm start again, the share mounting fails. The solution, for me, continues to be:
fin vm stop
change to a a command line with administrator privileges and issue the command:
net share <sharename> /delete
(now <sharename> is something like docksal-c)
fin vm start

Meanwhile, I moved to using the native Docker for Windows and it is working great. I really appreciate your work on this front and the ability to now set permanently the native apps mode.

unknownterritory picture unknownterritory on 4 Jun 2017

@unknownterritory interesting. When it works, does restarting the VM break the share(s) (fin vm restart) or does this only happen when you reboot or put the host to sleep? What is the error, that you are getting during fin vm start (please attach the full output if you can)?

lmakarov picture lmakarov on 5 Jun 2017

I'm going to close this issue due to inactivity and no recent reports.

If anyone is still having problems with shares on Windows, please post details here.

lmakarov picture lmakarov on 5 Aug 2017

There is a new "problem on the block" with SMB shares on Windows 10 - SMBv1 protocol is disabled in Windows 10 Fall Creators Update. Tracked here: https://github.com/docksal/docksal/issues/382

All Windows 10 users are advised to more to the "native" Docker for Windows option - http://docksal.readthedocs.io/en/master/getting-started/env-setup-native/
At the moment, Windows 10 Pro+ is require to be able to run Docker for Windows (due to the Hyper-V dependency it has).

lmakarov picture lmakarov on 14 Nov 2017

I'm having a similar issue, using WSL/Ubuntu and docker native:

[~/projects/boilerplate-drupal8] $ fin init
 Step 1  Initializing stack...
Removing containers...
Removing boilerplate-drupal8_cli_1 ... done
Removing boilerplate-drupal8_db_1  ... done
Removing network boilerplate-drupal8_default
Removing volume boilerplate-drupal8_cli_home
Removing volume boilerplate-drupal8_project_root
Removing volume boilerplate-drupal8_db_data
Volume docksal_ssh_agent is external, skipping
Key 'id_rsa' already loaded in the agent. Skipping.
Starting services...
Creating network "boilerplate-drupal8_default" with the default driver
Creating volume "boilerplate-drupal8_cli_home" with default driver
Creating volume "boilerplate-drupal8_project_root" with local driver
Creating volume "boilerplate-drupal8_db_data" with default driver
Creating boilerplate-drupal8_db_1  ... error
Creating boilerplate-drupal8_cli_1 ...

ERROR: for boilerplate-drupal8_db_1  Cannot start service db: error while mounting volume '/var/lib/docker/volumes/boilerplate-drupal8_project_root/_data': error while mounting volume with options: type='none' device='/home/gmarra/projects/boilerplate-drupal8' o='bind': no such file or dCreating boilerplate-drupal8_cli_1 ... error

ERROR: for boilerplate-drupal8_cli_1  Cannot start service cli: error while mounting volume '/var/lib/docker/volumes/boilerplate-drupal8_project_root/_data': error while mounting volume with options: type='none' device='/home/gmarra/projects/boilerplate-drupal8' o='bind': no such file or directory

ERROR: for db  Cannot start service db: error while mounting volume '/var/lib/docker/volumes/boilerplate-drupal8_project_root/_data': error while mounting volume with options: type='none' device='/home/gmarra/projects/boilerplate-drupal8' o='bind': no such file or directory

ERROR: for cli  Cannot start service cli: error while mounting volume '/var/lib/docker/volumes/boilerplate-drupal8_project_root/_data': error while mounting volume with options: type='none' device='/home/gmarra/projects/boilerplate-drupal8' o='bind': no such file or directory
ERROR: Encountered errors while bringing up the project.

Fin sysinfo:

[~/projects/boilerplate-drupal8] $ fin sysinfo
███  OS
WSL Ubuntu 18.04
Linux W8B5VW52 4.4.0-17763-Microsoft #379-Microsoft Wed Mar 06 19:16:00 PST 2019 x86_64 x86_64 x86_64 GNU/Linux

███  ENVIRONMENT
MODE : Docker Desktop

███  FIN
fin version: 1.85.1

███  DOCKER COMPOSE
EXPECTED VERSION: 1.23.2
docker-compose version 1.23.2, build 1110ad01
docker-py version: 3.6.0
CPython version: 3.6.7
OpenSSL version: OpenSSL 1.1.0f  25 May 2017

███  DOCKER
EXPECTED VERSION: 18.09.2

Client: Docker Engine - Community
 Version:           18.09.2
 API version:       1.39
 Go version:        go1.10.8
 Git commit:        6247962
 Built:             Sun Feb 10 04:11:47 2019
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          18.09.2
  API version:      1.39 (minimum version 1.12)
  Go version:       go1.10.6
  Git commit:       6247962
  Built:            Sun Feb 10 04:13:06 2019
  OS/Arch:          linux/amd64
  Experimental:     false

███  DOCKSAL: PROJECTS
project             STATUS                       virtual host                                             project root
projects            Up 26 minutes (healthy)      projects.docksal,*.projects.docksal,projects.docksal.*   /home/gmarra/projects
nysca               Up About an hour (healthy)   nysca.docksal,*.nysca.docksal,nysca.docksal.*            /home/gmarra/projects/NYSCA

███  DOCKSAL: VIRTUAL HOSTS
*.nysca.docksal
*.projects.docksal
nysca.docksal.*
nysca.docksal
projects.docksal.*
projects.docksal

███  DOCKSAL: DNS
curl: (6) Could not resolve host: dns-test.docksal
ERROR: Requesting http://dns-test.docksal failed!

███  DOCKER: RUNNING CONTAINERS
CONTAINER ID        IMAGE                     COMMAND                  CREATED             STATUS                       PORTS                                                       NAMES
3998a0f06fd0        docksal/ssh-agent:1.2     "docker-entrypoint.s…"   19 minutes ago      Up 19 minutes (healthy)                                                                  docksal-ssh-agent
8787bc26a4e4        docksal/dns:1.1           "docker-entrypoint.s…"   19 minutes ago      Up 19 minutes (healthy)      192.168.64.100:53->53/udp                                   docksal-dns
264631c1588b        docksal/vhost-proxy:1.5   "docker-entrypoint.s…"   19 minutes ago      Up 19 minutes (healthy)      192.168.64.100:8080->80/tcp, 192.168.64.100:8443->443/tcp   docksal-vhost-proxy
3749b823990b        docksal/apache:2.4-2.3    "httpd-foreground"       26 minutes ago      Up 26 minutes (healthy)      80/tcp, 443/tcp                                             projects_web_1
3631af43ff3a        docksal/cli:2.1-php7.1    "/opt/startup.sh sup…"   26 minutes ago      Up 26 minutes (healthy)      22/tcp, 3000/tcp, 9000/tcp                                  projects_cli_1
b051556fc2df        docksal/mysql:5.6-1.4     "docker-entrypoint.s…"   26 minutes ago      Up 26 minutes (healthy)      0.0.0.0:32776->3306/tcp                                     projects_db_1
e0b57d816c96        docksal/apache:2.4-2.3    "httpd-foreground"       About an hour ago   Up About an hour (healthy)   80/tcp, 443/tcp                                             nysca_web_1
e36933793733        docksal/cli:2.1-php7.1    "/opt/startup.sh sup…"   About an hour ago   Up About an hour (healthy)   22/tcp, 3000/tcp, 9000/tcp                                  nysca_cli_1
1ecf5fcce590        docksal/mysql:5.6-1.4     "docker-entrypoint.s…"   About an hour ago   Up About an hour (healthy)   0.0.0.0:32775->3306/tcp                                     nysca_db_1

███  DOCKER: NETWORKS
NETWORK ID          NAME                          DRIVER              SCOPE
c95768b67442        _default                      bridge              local
ff9b150a1263        boilerplate-drupal8_default   bridge              local
83635e50a581        bridge                        bridge              local
ba3ec082ddc5        host                          host                local
92fabd6632da        none                          null                local
d766a34df47f        nysca_default                 bridge              local
11c0cfd9fe69        projects_default              bridge              local

███  DOCKER DESKTOP
EXPECTED VERSION: 2.0.0.3

Docker Desktop
Version: 2.0.0.3 (31259)
Channel: stable
Sha1: 8858db33c8692b69de9987a5d672798d778735b2
OS Name: Windows 10 Enterprise
Windows Edition: Enterprise
Windows Build Number: 17763

███  HDD Usage
Caption  FreeSpace      Size
C:       90206433280    254859341824
D:       1000020795392  1000202039296
E:
O:       3725360779264  28312424415232
V:       6906279559168  51896948834304
gmarra36 picture gmarra36 on 19 Apr 2019

@greg-marra you cannot use linux home folder to store your projects. use a drive accessible to windows

achekulaev picture achekulaev on 19 Apr 2019
👍1

Hey, thanks for that step, I moved the project to:

C:\Users\GMarraprojects\NYSCA and am still getting the error

gmarra36 picture gmarra36 on 22 Apr 2019

@greg-marra most likely you did not share your drives as described in step 4 here https://docs.docksal.io/getting-started/setup/#install-windows-docker-for-windows

achekulaev picture achekulaev on 23 Apr 2019
Was this page helpful?
0 / 5 - 0 ratings

Related issues

ArtuGit picture ArtuGit  ·  19Comments
lmakarov picture lmakarov  ·  18Comments
tbtmuse picture tbtmuse  ·  22Comments
mikecrittenden picture mikecrittenden  ·  17Comments
amjad-wp picture amjad-wp  ·  18Comments