init script not working on windows

[giji]

Hello
on Windows 10 64bit. I followed all the steps described on the corresponding GitHub page and subzero base-project which takes me through the questions and finishes with "Downloading the base project..". But my project directory always stays empty afterwards. Switching between between the options (subzero or pure postgrest, database structure/migrations here yes/no) makes no difference, neither does running it within a Powershell session with admin privileges.

[ruslantalpa]

@giji i've pushed a new version 0.1.24
can you please check if the base-project command works? (i am unable at this point to checking myself since i can not run docker inside a VM it seems)

[giji]

@ruslantalpa no, still not working
does not work :
base project
dashboard
works:
watch

if launching directly respective js files seems partly to work
the problem i think is in commander package/commands
will try to find a problem

[ruslantalpa]

@giji
can you please post the output of docker info?
i suspect you are on windows home, using docker tool box and you are actually running docker in virtual box...

[ruslantalpa]

quite disappointed to find out the root of the problem is in a popular node module and it simply does not work on windows :(
there is a PR waiting to be merged for over a year tj/commander.js#604
I guess i'll have to fork and fix it myself

[giji]

@ruslantalpa
no i have docker installed on hyper-v , anyway latest Windows 10 has hyper-v installed i have installed Ubuntu vm inside and then docker and then subzero works flawlessly, i would recomend to leave this way and wait until the change will go upstream.
p.s do you still need docker info ?

[ruslantalpa]

since last post I discovered another bunch of bugs and fixed them.
docker info (especially from your windows pro with hyper-v) will help since I have some special logic to distinguish between the two scenarios.

i'll have the fixes up this week. Thank you for the feedback

[giji]

no, thank you for amazing project 👍
output for docker info:

Images: 7
Server Version: 18.06.1-ce
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 468a545b9edcd5932818eb9de8e72413e616e86e
runc version: 69663f0bd4b60df09991c08812a60108003fa340
init version: fec3683
Security Options:
seccomp
Profile: default
Kernel Version: 4.9.93-linuxkit-aufs
Operating System: Docker for Windows
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 1.934GiB
Name: linuxkit-00155dc6821a
ID: KG4Q:RJW5:ODXE:MMOB:3FY6:KSJ6:5QYR:NLVC:7OSD:EVXM:PP7T:CPLW
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
File Descriptors: 22
Goroutines: 47
System Time: 2018-09-27T21:24:34.575198Z
EventsListeners: 1
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false

P.s will be waiting for another bug fix :)

[ruslantalpa]

@giji
I have the fixes under this branch https://github.com/subzerocloud/subzero-cli/tree/windows_fixes

if you can, please see if it works on your system (uninstall the current one before it with npm uninstall -g subzero-cli)

• clone the branch
• npm install
• npm run build ; npm link

the git style subcommands do not work yet because of that bug, but you can run them as such

subzero-dashboard      Open dashboard
subzero-migrations     Manage database migrations process (experimental)
subzero-cloud          Actions for your subzero.cloud account
subzero-watch          Live code reloading for SQL/Lua/Nginx configs
subzero-base-project   Download a base project

thank you for the feedback

[giji]

Hello Ruslan sorry i was out, sure i will test and get back to you.

[giji]

Works flawlessly :) 👍

[ruslantalpa]

there is a new release v0.1.25 so hopefully this is solved, + I recently moved to windows so i'll be able to catch these problems faster :)
thank you for the feedback