mnabeel.
06/15/2024, 11:12 AMProperB 👹
06/20/2024, 1:39 PMCreate agent failed. InvalidResourceState( “Node default/gke......... is in invalid state: too full with 118 pods”, )
Could someone assist why this is happening, i can't see why too many pods would be an issue but happy to be proven wrong.William
06/24/2024, 9:05 AMWilliam
06/24/2024, 9:05 AMmchow
06/24/2024, 8:55 PMKostya O
07/04/2024, 2:18 PMmnabeel.
07/05/2024, 9:08 AMkubectl get pods
and kubectl apply -f ....
work on my terminal, I am authenticated in the cluster with admin permissions so MirrorD should have no difficulty spawning the MirrorD agentKostya O
07/08/2024, 11:17 AMCegh
07/11/2024, 2:12 PM{
"target": {
"path": "deployment/opencost/container/opencost",
"namespace": "opencost"
},
"feature": {
"fs": {
"mode": "write"
},
"env": {
"include": "*"
}
}
}
that's my error:
2024-07-11T17:10:10.701429+03:00 INF starting download of "https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonEC2/current/eu-west-2/index.json", which is quite large ...
Proxy error, connectivity issue or a bug.
You may report it to us on https://github.com/metalbear-co/mirrord/issues/new?assignees=&labels=bug&projects=&template=bug_report.yml
io failed: Resource temporarily unavailable (os error 35)
2024-07-11T17:10:29.109697+03:00 ERR Storage Stat Error: Failed to stat file: stat /models/aws.json: invalid argument
how can I debug this?Dijkstra
07/12/2024, 6:25 PMauggie
07/31/2024, 11:00 AMmirrord
to debug my Kubernetes pod, and I could really use some help. Here's the issue I'm facing:
I am trying to use mirrord
to run my Go application and target a Kubernetes pod, but I keep getting the following error:
2024-07-31T12:52:49.253+0200 ERROR controller-runtime.source.EventHandler source/kind.go:76 failed to get informer from cache {"error": "failed to get restmapping: failed to get server groups: Get \"https://127.0.0.1:6443/api\": dial tcp 127.0.0.1:6443: connect: connection refused"}
Additionally, I have the following mirrord
configuration file:
mirrord.json:
json
{
"accept_invalid_certificates": false,
"skip_processes": "ide-debugger",
"kubeconfig": "~/.kube/config",
"kube_context": "default",
"target": {
"path": "pod/operator-controller-manager-86bb6b4c79-t5dsl",
"namespace": "c8yedge"
},
"feature": {
"network": {
"incoming": "mirror",
"outgoing": true
},
"fs": "read",
"env": true
}
}
shell
❯ kgp
NAME READY STATUS RESTARTS AGE
operator-controller-manager-86bb6b4c79-t5dsl 1/1 Running 0 40m
mirrord-agent-zeoqsitccd-cbc7t 1/1 Running 0 5m13s
❯ kl mirrord-agent-zeoqsitccd-cbc7t
agent ready - version 3.112.0
2024-07-31T10:52:11.782957Z WARN ThreadId(07) mirrord_agent::outgoing::udp: interceptor_task -> no messages left
Any insights on why this might be happening or how to resolve it would be greatly appreciated!
Thanks in advance for your help!eugene
08/01/2024, 11:02 AMmirrord exec -c --steal --target pod/my-pod --config-file kubie-config.yaml ./.mirrord/mirrord.json
x mirrord exec
✓ running on latest (3.112.0)! Error: × Failed to verify mirrord config: mirrord-config: `unknown field `clusters`, expected one of `accept_invalid_certificates`, `skip_processes`, `skip_build_tools`, `connect_tcp`, `operator`, `kubeconfig`, `sip_binaries`, `target`, `agent`, `feature`, `telemetry`, `kube_context`, `internal_proxy`,
│ `use_proxy`, `experimental` at line 2 column 1`!
├─▶ mirrord-config: `unknown field `clusters`, expected one of `accept_invalid_certificates`, `skip_processes`, `skip_build_tools`, `connect_tcp`, `operator`, `kubeconfig`, `sip_binaries`, `target`, `agent`, `feature`, `telemetry`, `kube_context`, `internal_proxy`, `use_proxy`, `experimental` at line 2
│ column 1`!
╰─▶ unknown field `clusters`, expected one of `accept_invalid_certificates`, `skip_processes`, `skip_build_tools`, `connect_tcp`, `operator`, `kubeconfig`, `sip_binaries`, `target`, `agent`, `feature`, `telemetry`, `kube_context`, `internal_proxy`, `use_proxy`, `experimental` at line 2 column 1
help: Inspect your config file and arguments provided.
{
"kubeconfig": "kubie-configf.yaml",
"feature": {
"network": {
"incoming": {
"mode": "steal",
"ignore_ports": [
8081
],
"http_filter": {
"header_filter": "DEBUG"
}
}
},
"fs": "read",
"env": true
}
}
Emanuele
08/09/2024, 3:00 PMPrasta Maha
08/12/2024, 10:12 AM{
"feature": {
"env": true,
"fs": {
"mode": "read"
},
"network": {
"incoming": {
"mode": "steal",
"http_filter": {
"header_filter": "X-Mirror: testing",
"ports": [
80,
8080
]
}
}
}
}
}
mnabeel.
08/14/2024, 3:27 PMfeature:
split_queues:
my-first-queue:
queue_type: SQS
message_filter:
wows: "so wows"
Does this mean that if a message is added to the SQS with property wow
set to so wows
then the remote pod can still consume it, but if a local service is running with this config, then the local service will have priority over this message?Emanuele
08/19/2024, 12:54 PMEmanuele
08/20/2024, 10:13 AMJohn Dough
09/25/2024, 3:08 PM"network": {
"incoming": {
"mode": "steal",
"http_filter": {
"header_filter": "^User-Agent: Mozilla\/5.0 \\(Macintosh; Intel Mac OS X 10\\.15; rv\\:130.0\\) Gecko\/20100101 Firefox\/130\\.0",
"ports": [3000]
}
}
}
}
I am stealing traffic from my system/browser specifically(is there a better way to do this?)John Dough
09/25/2024, 3:08 PM"agent": {
"ephemeral": true
}
The reason I mention this is I am using VS Code extension and I have noticed that the proper way is to click that button next to mirrord in the bottom toolbar to make everything work properly. I killed processes with ctrl+c a few times and that resulted in errors in the cluster(containers not coming up).
Today, when I sshed into a container, I got this as output:
> kubectl exec --namespace="allex-accounts" --stdin --tty accounts-96fc6966c-2mk2k -- sh
Defaulted container "accounts" out of: accounts, mirrord-agent-srtm0at7ti (ephem), mirrord-agent-5ds4u0rgio (ephem), mirrord-agent-vkc3cxzcli (ephem), mirrord-agent-dluhpgynee (ephem), mirrord-agent-7y1prbmfl9 (ephem), mirrord-agent-v3xpaqejfw (ephem), mirrord-agent-lmyjkv4ma7 (ephem), mirrord-agent-iq2hv8wb8o (ephem), mirrord-agent-ebk6ecmru8 (ephem), mirrord-agent-vj56mq0yll (ephem), mirrord-agent-oc1yrlxobl (ephem), mirrord-agent-naqh6vmumk (ephem), mirrord-agent-1c3vc8ubpa (ephem), mirrord-agent-th2mjxxloo (ephem), mirrord-agent-2ytfjofd2c (ephem), mirrord-agent-z2n4hm0sbn (ephem), mirrord-agent-c5efsk1bs5 (ephem), mirrord-agent-0zmadv6ov9 (ephem), mirrord-agent-ff97gfch9x (ephem), mirrord-agent-sdtpoz4s2z (ephem), mirrord-agent-fe4e6z0vuh (ephem), mirrord-agent-fro5i3odhp (ephem), mirrord-agent-irviob5pxw (ephem), mirrord-agent-ugqbpvsdm5 (ephem), mirrord-agent-nk9zn0mrqm (ephem), mirrord-agent-bhtqiphy4v (ephem), mirrord-agent-dm2prnlef6 (ephem), mirrord-agent-8coyd3uu2r (ephem), mirrord-agent-d1erwnuq1h (ephem)
Sorry if I am not making much sense but I just want to use it correctly so that I can do a demo for everyone.Crucios
09/26/2024, 7:09 AMJohn Dough
09/30/2024, 2:45 PM0x6a77
10/21/2024, 2:35 AMdig
fails to reach the nameserver from etc/resolv.conf
. we've tried --networking=host
and --networking=bridge
. (it seems like a networking problem, but mirrord network model is a bit opaque so we can't tell if the ifconfig
makes sense or not)
any docs or pointers on how mirrord can intercept a local docker container debug from pycharm/intellij?
thanks!Emanuele
10/23/2024, 12:18 PMMr.Kerwood
11/29/2024, 1:04 PMTheTrueAmigo
02/03/2025, 1:00 PMkubectl get pods
in the relevant namespace.\n 2. If you don't see any mirrord-agent-[...]
pods, then try running kubectl get jobs
, and kubectl describe mirrord-agent-[...]
.\n Make sure it is able to fetch the agent image, it didn't fail due to lack of resources, etc.\n\n- If you're still stuck:\n\n>> Please open a new bug report at https://github.com/metalbear-co/mirrord/issues/new/choose\n\n>> Or join our Discord https://discord.gg/metalbear and request help in #950020257156833340\n\n>> Or email us at hi@metalbear.co\n\n","labels": [],"related": []}TheTrueAmigo
02/03/2025, 1:00 PMpraveensanap
02/17/2025, 4:43 AMthorstenhirsch
03/04/2025, 1:25 PMFailed to create mirrord-agent: ServiceError: client error (Connect)
. I've uploaded the image to the Artifactory instance from which GKE pulls all images successfully. I can even start a container manually like so: kd run mirrord-agent --image="artifactory.local:5200/metalbear-co/mirrord:latest"
But it seems like mirrord doesn't respect the corresponding setting in its mirrord.json: "agent": { "image": "artifactory.local:5200/metalbear-co/mirrord:latest" }
pirtea07
04/07/2025, 2:07 PM{
"accept_invalid_certificates": false,
"skip_processes": "ide-debugger",
"kube_context": "{{ get_env(name="MIRRORD_KUBE_CONTEXT", default="undefined") }}",
"target": {
"path": "{{ get_env(name="MIRRORD_TARGET", default="undefined") }}",
"namespace": "{{ get_env(name="MIRRORD_NAMESPACE", default="undefined") }}"
},
"connect_tcp": null,
"agent": {
"log_level": "mirrord=debug",
"namespace": "{{ get_env(name="MIRRORD_NAMESPACE", default="undefined") }}",
"image": "ghcr.io/metalbear-co/mirrord:latest",
"image_pull_policy": "IfNotPresent",
"ttl": 30,
"ephemeral": false,
"communication_timeout": 30,
"startup_timeout": 360,
"network_interface": "eth0"
},
"feature": {
"env": { },
"fs": {
"mode": "write"
},
"network": {
"incoming": "steal"
}
}
}
https://cdn.discordapp.com/attachments/1001193615474827264/1358805343970394233/image.png?ex=67f52d97&is=67f3dc17&hm=449373546a44319240a1581e0a6ca32047cc3e4ee655e486386253fc5b1dcaa2&staeff.
04/18/2025, 8:28 AM