docksal: fin update doesn't install dependencies, only self-updates, on Windows 10 64-bit by default
Description
I cannot use docksal on a Windows 64-bit system because
- babun does not have a stable 64-bit release / process.
- cygwin64 does have a stable 64-bit release that babun’s documentation recommends to use instead of babun, but docksal is having issues detecting custom commands or running update.
Steps to reproduce the issue:
With babun
- Try to install babun
- Get Unexpected error message. Give up. Do not use docksal?
With cywgin64
- Install cygwin64 via 64-bit installer. Make sure to include php and curl packages that are required for Drupal 8.4 core development.
- Downloaded fin shell script to
C:\cygwin64\usr\local\bin\. - Tried running
fin vm startper instructions. Failed beacuse docker not available. - Tried running
fin updateper failed command above’s recommendation. Fails to run fin update because the update command usessudoinstead of trying the winsudo function that fin defines. - Tried just running
fin init:git clone https://github.com/BrianGilbert/docksal-core-sprintcd docksal-core-sprintfin init
- Try hacking fin shell script and keep running into hard errors. Give up.
Describe the results you received:
Tried to run fin vm start per docksal instructions…
$ fin vm start
docker-machine executable was not found. (Try running 'fin update')
Okay, now I tried fin update…
$ fin update
Updating fin...
/usr/local/bin/fin: line 3222: sudo: command not found
ERROR: Could not write /usr/local/bin/fin.updated
Okay, let’s hack the update function to use winsudo instead…
$ fin update
Updating fin...
/usr/local/bin/fin: line 3231: /usr/local/bin/fin.updated: No such file or directory
fin downloaded...
/usr/local/bin/fin: line 3235: /usr/local/bin/fin.updated: No such file or directory
Describe the results you expected:
I expect that I can use docksal on a Windows 10 64-bit system because the System Requirements for docksal do not mention needing to use 32-bit binaries.
Output of fin config:
fin config output
$ fin config output
ERROR: No configuration files found.
Expected in C:/cygwin64/c/dev/docksal-core-sprint/.docksal/docksal.yml
But the file does in fact exist at /cygdrive/c/dev/docksal-core-sprint/.docksal/docksal.yml so for some reason fin config is using the Windows path and not the cygdrive path.
Output of fin sysinfo:
fin sysinfo output
$ fin sysinfo
███ OS & BASICS
CYGWIN_NT-10.0 MACHINENAME 2.8.2(0.313/5/3) 2017-07-12 10:58 x86_64 Cygwin
Microsoft Windows [Version 10.0.14393]
fin version: 1.26.2
Mode: VirtualBox VM
███ DOCKER
DOCKER_HOST:
/usr/local/bin/fin: line 3952: docker: command not found
Docker:
███ DOCKER COMPOSE
/usr/local/bin/fin: line 3955: docker-compose: command not found
Docker Compose:
███ VIRTUALBOX
5.1.26r117224
███ NETWORK INTERFACES
Name: VirtualBox Host-Only Ethernet Adapter #4
GUID: b9fa8fae-681d-43c6-a9e0-a6a7bf345a3c
DHCP: Disabled
IPAddress: 192.168.253.1
NetworkMask: 255.255.255.0
IPV6Address: fe80:0000:0000:0000:8c39:7422:7a53:ad4b
IPV6NetworkMaskPrefixLength: 64
HardwareAddress: 0a:00:27:00:00:0a
MediumType: Ethernet
Status: Up
VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #4
Name: VirtualBox Host-Only Ethernet Adapter #3
GUID: fe6eed92-3843-477c-aec9-5b3d5de3869b
DHCP: Disabled
IPAddress: 192.168.56.1
NetworkMask: 255.255.255.0
IPV6Address: fe80:0000:0000:0000:59d7:c791:196f:97b1
IPV6NetworkMaskPrefixLength: 64
HardwareAddress: 0a:00:27:00:00:0c
MediumType: Ethernet
Status: Up
VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #3
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 16 (7 by maintainers)
You do not provide any solid arguments to back your opinion about “poor behavior”. Arguments like this:
are applicable to any installer whether it’s EXE, MSI, PKG or even apt-get. Exception is only DMG files on macOS where user just copies a file.
Furthermore, a ton of popular software uses this way of installation. To name a few: Brew, Composer, Docker itself used to use it for a long time and get.docker.com still provides a robust way to install Docker on Linux.
One line installer helps novice users to get software installed. And we have seen tremendous positive feedback from that group of users after we moved from 4 commands to 1, because for them those 4 lines make no more sense than 1 line.
To conclude:
With all said above I find this way of installation not only not poor, but purely great for command line utilities.
@mradcliffe, glad you got it working in both Linux and Windows.
It is still not clear why you had to hack anything. Docksal’s install/update process works just fine on a clean Mac, Linux (including automated tests in Travis CI) or Windows system, assuming you follow the instructions as written.
Being not able to reproduce the issues you reported, I can only assume, that you have some kind of custom setup/permissions/etc. (which we know nothing about), which is causing those difficulties in your case.