ITxPT/DATA4PTTools

is it ok with Docker Desktop on Windows 10 ?

Closed this issue · 3 comments

I have installed the tool on windows 10using Docker Desktop

docker run -it lekojson/greenlight -i testdata and docker run -it lekojson/greenlight --help are Ok, but everything elseis reslulting in a nice

panic: runtime error: invalid memory address or nil pointer dereference
   panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0x821e18]

goroutine 1 [running]:
github.com/concreteit/greenlight.(*Validator).Validate.func1()
   /usr/local/greenlight/validator.go:33 +0x18
panic({0xb99080, 0x123e2f0})
   /usr/local/go/src/runtime/panic.go:1038 +0x215
github.com/concreteit/greenlight.(*Validator).Validate(0xc0001b2980, 0x0)
   /usr/local/greenlight/validator.go:36 +0x82
main.validate(0x1248540, {0xc80e3c, 0x2, 0x2})
   /usr/local/greenlight/cmd/validate.go:243 +0x5b0
github.com/spf13/cobra.(*Command).execute(0x1248540, {0xc0001cd2e0, 0x2, 0x2})
   /go/pkg/mod/github.com/spf13/cobra@v1.2.1/command.go:860 +0x5f8
github.com/spf13/cobra.(*Command).ExecuteC(0x12482c0)
   /go/pkg/mod/github.com/spf13/cobra@v1.2.1/command.go:974 +0x3bc
github.com/spf13/cobra.(*Command).Execute(...)
   /go/pkg/mod/github.com/spf13/cobra@v1.2.1/command.go:902
main.main()
   /usr/local/greenlight/cmd/root.go:19 +0x25

any specific syntax to provide windows files from Powershell (or any other environment I should use) ?

I googled around and most often found things like "trying to copy a file in a dockerfile to a destination with a space in it. You’re likely to get an error about how a path doesn’t exist. If you Google this problem you get great advice which basically adds up to “Don’t put spaces in your file paths”. ! I was wondering if I should remove "Programme (x86)" ;-) ????

Anyway, using a dedicated short path without space allows to overcome the issue (however SIGSEGV is not really explicit for such an issue)

image
How to get more than just this from the "docker run" command ?

This should be fixed since the rework of the core tool