Handle Job/Pod creation errors in mirrord-layer about mirrord HOT 7 CLOSED

No worries @camerondurham, let us know you need any help.

from mirrord.

Hi, Just saw this in TWIR 446. I'm interested in taking this issue if nobody else claims it. Thanks!

from mirrord.

@camerondurham I have assigned you the issue, thanks!

from mirrord.

Really sorry for not sending any updates. I haven't forgotten about this and will be able to work on it Friday.

from mirrord.

I was very wrong about that last update, was not able to make much progress last week. Apologies, on-call at work ended up eating all my time but I'm setting aside time this weekend even though this issue. I know this will end up being a pretty small, trivial change so again sorry for making a bigger deal out of this too.

One thing I wanted to check on is it seems the best dev environment for this is an x86 Linux machine? I had tried my M1 w/emulated x86 containers and native arm devcontainers and had various errors (can document this somewhere, don't have errors on me right now). I did see #114 which suggests M1 may not be supported yet so that's not a surprise.

I still have a workaround of using GH codespaces or just a Linux VM which work pretty well.

Thanks!

from mirrord.

Actually, a few of us do use M1s. We're currently having trouble working with minikube, so we're relying on remote clusters to test, but otherwise, things seem to be working. If you can elaborate on where you ran into trouble we might be able to help.
And don't worry about making a big deal out of it - it's really important for us to make onboarding easier for new contributors, so if we're able to get some insights from your attempts, all the better.

from mirrord.

The most basic dumb issue I was having was basically the same as this, compiling project in an arm based container on M1 and not able to build all the dependencies: #135

Compiling frida-gum-sys v0.3.4
error[E0432]: unresolved import `_frida_g_object_unref`
  --> /usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/frida-gum-sys-0.3.4/src/lib.rs:25:9
   |
25 | pub use _frida_g_object_unref as g_object_unref;
   |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ no external crate `_frida_g_object_unref`

For more information about this error, try `rustc --explain E0432`.
The following warnings were emitted during compilation:

warning: Frida gum devkit not found, downloading from https://github.com/frida/frida/releases/download/15.1.17/frida-gum-devkit-15.1.17-linux-arm64.tar.xz...

error: could not compile `frida-gum-sys` due to previous error

I think a possible solution was already mentioned for the compiling frida-gum-sys step: #135 (reply in thread)

I can try the suggestions from that discussion, I haven't yet but looks like someone else was already having those issues and working on some sharable resources for compiling which would be awesome.

What I tried already:

pip install frida-tools

npm install frida

wget https://github.com/frida/frida/releases/download/15.1.17/frida-gum-devkit-15.1.17-linux-arm64.tar.xz
tar xf frida-gum-devkit-15.1.17-linux-arm64.tar.xz

# this is almost definitely wrong, just trying to follow this without checking where these files should actually live https://lib.rs/crates/frida-gum-sys
mv frida* libfrida* /usr/local/

I was also thinking of manually trying to install the frida devkit (the steps for this dep I think: https://lib.rs/crates/frida-gum-sys) and setup in the dev container but not sure if that's a feasible solution...

In the meantime I can use GH codespaces or an x86 Linux VM where the project compiles just fine 😄. I think I can try playing around with the devcontainer project and see if I can add some platform specific build steps but no promises since idk if that will work yet!

from mirrord.