Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mirrord error: Failed to create mirrord-agent: None runtime data for non-targetless agent. This is a bug. #3056

Open
dbeilin opened this issue Feb 3, 2025 · 5 comments
Assignees
Labels
bug Something isn't working

Comments

@dbeilin
Copy link
Contributor

dbeilin commented Feb 3, 2025

Bug Description

Hello,
Since the update to 3.65.0, any time we start a remote-dev session, we see the following error:

mirrord error: Failed to create mirrord-agent: None runtime data for non-targetless agent. This is a bug.

Image

We reverted to 3.64.0 for now.

Steps to Reproduce

  1. Open repo in DevContainer
  2. Toggle Mirrord on
  3. Run Debug

Backtrace

mirrord layer logs

mirrord intproxy logs

mirrord agent logs

mirrord config

mirrord CLI version

No response

mirrord-agent version

No response

mirrord-operator version (if relevant)

No response

plugin kind and version (if relevant)

No response

Your operating system and version

MacOS 15.2

Local process

Debug (F5), which runs a default launch.json

Local process version

No response

Additional Info

No response

    *};*

Thank you for contributing to mirrord!

Please make sure you added a CHANGELOG file in changelog.d/ named issue_number.category.md.

For example, 1054.changed.md or +towncrier.added.md (if no issue).

@dbeilin dbeilin added the bug Something isn't working label Feb 3, 2025
@Razz4780
Copy link
Contributor

Razz4780 commented Feb 4, 2025

Hey @dbeilin, can you provide some more context to this issue?

  1. Do you use mirrord via IntelliJ plugin / VSCode extension?
  2. What does your mirrord config look like?

@dbeilin
Copy link
Contributor Author

dbeilin commented Feb 4, 2025

Hey @Razz4780 sorry for not providing more details.

  1. It's the VS Code extenion
  2. My config:
{
  "target": "deployment/forrest/container/<service>",
  "accept_invalid_certificates": false,
  "feature": {
    "network": {
      "incoming": "mirror",
      "outgoing": true
    },
    "fs": "read",
    "env": {
      "exclude": "*_SUB"
    }
  },
  "agent": {
    "ephemeral": true,
    "privileged": true
  },
  "operator": false
}

Copy link
Contributor

Razz4780 commented Feb 4, 2025

Thanks! I found the error in the VSCode extension code, I'll let you know when we release the fix

@Razz4780 Razz4780 self-assigned this Feb 4, 2025
Copy link
Contributor

Razz4780 commented Feb 4, 2025

I've just released extension 3.65.1, can you try it out and check if the problem is fixed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants