Skip to content

Can't run extension with Rancher Desktop #54

@ityshchenko

Description

@ityshchenko

Describe the bug

Can't confirm the last configuration step on the first install.

Steps to Reproduce

  1. Install rancher-desktop
  2. Run rdctl extension install localstack/localstack-docker-desktop:v0.5.3
  3. Open rancher-desktop app.
  4. Select LocalStack at the left pane.
  5. Press Next and Next.

Expected behavior

Continue setup.

Screenshots

Image

Additional context

  • rancher-desktop 1.17.1
  • container engine: dockerd/moby
  • virtual machine type: Apple VZ
  • mount type: virtiofs

References

Activity

Pive01

Pive01 commented on Feb 10, 2025

@Pive01
Collaborator

hi @ityshchenko thanks for submitting your issue....Seems like I'm unable to reproduce the behaviour...not sure if on rancher desktop works the same but could you

  • uninstall the extension (or clear the volume)
  • install it again
  • run docker extension dev debug localstack/localstack-docker-desktop
  • do the initial setup flow again
    and report eventual strange errors in happening in the console? Thanks
ochaoui

ochaoui commented on Feb 14, 2025

@ochaoui

Hello @Pive01 ,

I have the same problem with Ubuntu on WSL2 and docker-desktop.
Here the logs of the extension :

Image

Any idea why it does not work ?

ityshchenko

ityshchenko commented on Feb 23, 2025

@ityshchenko
Author

@Pive01, for Rancher Desktop, the process is slightly different:

I executed the command /Applications/Rancher Desktop.app/Contents/MacOS/Rancher Desktop —remote-debugging-port=“8315” —remote-allow-origins=http://localhost:8315 to collect debug logs from the browser. The “close” and “confirm” buttons are ineffective, and I’m stuck on the final screen.

GET
http://localhost:8315/favicon.ico
[HTTP/1.1 404 Not Found 0ms]

Main._createAppUI: 10ms - timer ended [main.js:1:5072](http://localhost:8315/devtools/entrypoints/main/main.js)
Main._showAppUI: 181ms - timer ended [main.js:1:5072](http://localhost:8315/devtools/entrypoints/main/main.js)
Main._initializeTarget: 7ms - timer ended [main.js:1:5072](http://localhost:8315/devtools/entrypoints/main/main.js)
Main._lateInitialization: 0ms - timer ended [main.js:1:5072](http://localhost:8315/devtools/entrypoints/main/main.js)
Request Autofill.enable failed. {"code":-32601,"message":"'Autofill.enable' wasn't found"} [protocol_client.js:1:6923](http://localhost:8315/devtools/core/protocol_client/protocol_client.js)
Uncaught (in promise) ReferenceError: Highlight is not defined
    <anonymous> http://localhost:8315/devtools/ui/components/highlighting/highlighting.js:1
    r http://localhost:8315/devtools/ui/components/highlighting/highlighting.js:1
    instance http://localhost:8315/devtools/ui/components/highlighting/highlighting.js:1
    hideSearchHighlights http://localhost:8315/devtools/panels/elements/elements.js:8
    highlightSearchResultsInternal http://localhost:8315/devtools/panels/elements/elements.js:8
    updateTitle http://localhost:8315/devtools/panels/elements/elements.js:8
    onattach http://localhost:8315/devtools/panels/elements/elements.js:8
    insertChild http://localhost:8315/devtools/ui/legacy/legacy.js:3
    appendChild http://localhost:8315/devtools/ui/legacy/legacy.js:3
    appendChild http://localhost:8315/devtools/ui/legacy/legacy.js:3
    update http://localhost:8315/devtools/panels/elements/elements.js:8
    set rootDOMNode http://localhost:8315/devtools/panels/elements/elements.js:8
    documentUpdated http://localhost:8315/devtools/panels/elements/elements.js:8
    dispatchEventToListeners http://localhost:8315/devtools/core/common/common.js:1
    setDocument http://localhost:8315/devtools/core/sdk/sdk.js:1
    requestDocumentInternal http://localhost:8315/devtools/core/sdk/sdk.js:1
    requestDocument http://localhost:8315/devtools/core/sdk/sdk.js:1
    wasShown http://localhost:8315/devtools/panels/elements/elements.js:8
    notify http://localhost:8315/devtools/ui/legacy/legacy.js:1
    processWasShown http://localhost:8315/devtools/ui/legacy/legacy.js:1
    showWidgetInternal http://localhost:8315/devtools/ui/legacy/legacy.js:1
    show http://localhost:8315/devtools/ui/legacy/legacy.js:1
    materialize http://localhost:8315/devtools/ui/legacy/legacy.js:1
    promise callback*materialize http://localhost:8315/devtools/ui/legacy/legacy.js:1
    wasShown http://localhost:8315/devtools/ui/legacy/legacy.js:1
    notify http://localhost:8315/devtools/ui/legacy/legacy.js:1
    processWasShown http://localhost:8315/devtools/ui/legacy/legacy.js:1
    callOnVisibleChildren http://localhost:8315/devtools/ui/legacy/legacy.js:1
    processWasShown http://localhost:8315/devtools/ui/legacy/legacy.js:1
    callOnVisibleChildren http://localhost:8315/devtools/ui/legacy/legacy.js:1
    processWasShown http://localhost:8315/devtools/ui/legacy/legacy.js:1
    callOnVisibleChildren http://localhost:8315/devtools/ui/legacy/legacy.js:1
    processWasShown http://localhost:8315/devtools/ui/legacy/legacy.js:1
    callOnVisibleChildren http://localhost:8315/devtools/ui/legacy/legacy.js:1
    processWasShown http://localhost:8315/devtools/ui/legacy/legacy.js:1
    callOnVisibleChildren http://localhost:8315/devtools/ui/legacy/legacy.js:1
    processWasShown http://localhost:8315/devtools/ui/legacy/legacy.js:1
    showWidgetInternal http://localhost:8315/devtools/ui/legacy/legacy.js:1
    show http://localhost:8315/devtools/ui/legacy/legacy.js:1
    attachToDocument http://localhost:8315/devtools/ui/legacy/legacy.js:3
    presentUI http://localhost:8315/devtools/panels/screencast/screencast.js:1
    #k http://localhost:8315/devtools/entrypoints/main/main.js:1
    #S http://localhost:8315/devtools/entrypoints/main/main.js:1
    #v http://localhost:8315/devtools/entrypoints/main/main.js:1
    D http://localhost:8315/devtools/entrypoints/main/main.js:1
    <anonymous> http://localhost:8315/devtools/entrypoints/devtools_app/devtools_app.js:1
Pive01

Pive01 commented on Feb 24, 2025

@Pive01
Collaborator

From the logs of @ochaoui it looks like the frontend cannot talk to the backend...My next question is when you do start the extension is the backend also running? Aka can you guys see a container called localstack_localstack-docker-desktop-desktop-extension-service.
Image
If so can you see anything strange in the logs? From where the issue occurs seems like when the extensions calls the backend to save config on the volume the call fails

@ityshchenko your seems an UI error but quite unrelated though 🤔 ...still thanks for providing some info!

ochaoui

ochaoui commented on Mar 3, 2025

@ochaoui

@Pive01 I see no Service in docker desktop :( :

Image

Image

Besides installing the addon on docker desktop, do I need to install something else ?

Pive01

Pive01 commented on Jun 12, 2025

@Pive01
Collaborator

Hi @ityshchenko @ochaoui , we released a new version of the extension...could you give it another try and tell me if it works now? Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @ityshchenko@Pive01@ochaoui

        Issue actions

          Can't run extension with Rancher Desktop · Issue #54 · localstack/localstack-docker-extension