Hi, I tried make runbook v0.0.10

and I had this problem:

Error: Connection error.

This is my docker file:

FROM node:20.13.1-alpine

# Docker Scout -- Vulnerability Scanning solved
RUN apk upgrade busybox 
RUN apk upgrade openssl 

WORKDIR /usr/src/app

COPY ["package.json", "./"]
COPY [".env.example", "./.env"]

RUN npm install

COPY . .

RUN npm run build

EXPOSE 3000

CMD node ./dist/src/main.js

and this is my extension config:

Was there a problem with 4fc89a7 - I'm now only seeing local-user, even when there the user is logged in.

Reproduction

Log in to Docker Desktop and then run the "docker" runbook generation - what I'm seeing is that we still see local-user.

This is the code from the previous extension. Inline completion providers are part of the next version of the lsp spec but they have to be registered manually in the current version of VSCode.

  vscode.languages.registerInlineCompletionItemProvider(
    [{ language: "dockerfile" }, { language: "markdown" }],
    {
      provideInlineCompletionItems(
        document: vscode.TextDocument,
        position: vscode.Position,
        context: vscode.InlineCompletionContext,
        token: vscode.CancellationToken
      ): vscode.ProviderResult<
        vscode.InlineCompletionItem[] | vscode.InlineCompletionList
      > {
        return nativeClient.sendRequest("textDocument/inlineCompletion", {
          context: {
            uri: document.uri.toString(),
            position: position,
            triggerKind: context.triggerKind,
          },
        });
      },
    }
  );

This is why the # docker:command=... completion is now longer showing up.

Reproduction

1. Stop Docker engine
2. Start VScode
3. Choose "Generate runbook"

Can this be something closer to "No local Docker Engine detected" just so we can be more prescriptive.

This is so that you don't have to open/edit runbooks in order to bind commands.

The LSP now supports a request called docker/markdown-blocks which will cause the lsp to re-fire all of the current $bind/register notifications using whatever has been cached. If the runbook.md has ever been opened by the user on the current machine (the current docker-lsp volume) then you'll be notified of those cached volumes.