Henrik Sjööh

Hello! We are running into this as well. We have found a workaround that works for us, change the import like @alexcrichton said: > I believe you'll need to import...

it's works with our particular setup, i am not 100% sure it is a fix for all environments. Another option would be to rename `index_bg.js` to something else, `index_fg.js` perhaps?...

Hello! Your settings look good. The only visual feedback you should get is when there is a problem, so if you fire upp the playground, and remove the`:` after `"__main__"`,...

I see. It sounds a lot like the linting command is being run but it's not getting any output, so it might be a problem with sending things to the...

I’ll try and get out a version of the extension with a debug setting today

Good to know! Some questions: Are you running your docker commands in WSL? Do you have a docker executable in WSL or are you using the one that came with...

Thanks for your answers. I have released a new version of the extension with a debug setting, if you set `docker-linter.debug` to `true` you should get an output tab that...

there is a little dropdown to the right, where it says tasks. There should be a Docker Linter option.

It does indeed look like it's executing the command correctly but is unable to pass the contents of the file into the container.

It is the Windows path to the file. But VSCode should pull the contents directly from the buffer in the editor so the file path should not matter. I don’t...