-
Notifications
You must be signed in to change notification settings - Fork 92
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
"Error: No tarball found inside binary" (Mac & Linux only) #37
Comments
It looks like the tar unpack is failing. Just for fun, I wrote a .NET program that takes the packed EXE, seeks until it finds a valid gzip header and prints out the contents of the tarball. This works just fine, so the embedded tarball isn't corrupted. Yet, the runner can't unpack it. |
@rooju I'm getting this error in windows. Steps:
start.cmd:
To generate the exe: Now run the Re-pack the exe again ( without changing nothing, just generate the exe again). When I runing it again I got the error message:
If I delete all files from I noted also, that on the second attempt to run the I'm using the release v0.3.0 |
No idea why this worked, but I was encountering the same issue as above when I run a command like this:
And fixed it by adjusting the command to:
For some reason (not familiar enough with rust) it needed a different --output parameter filename than the |
It's been a while since I used this last, but from what I remember, the issue was something on my side, IIRC. Something about not having permissions to unpack/overwrite (I don't remember very well). The error message was totally not indicative of the actual issue. |
I have a set of binaries (application + dependency libraries) that I'm using warp to pack as part of my automated workflow. However, lately, the packed binary has been failing to run with a "No tarball found inside binary" error message.
This only happens on Mac and Linux (Ubuntu). The packed binary runs as expected on Windows.
Also, and this is weird, this was working until today.
I even tried running the warp packer manually, outside my workflow, to the same result: works on Windows, does not work on other platforms.
I should also mention that on all 3 platforms, the packed binary does have the gzip magic header that the runner is looking for.
Any idea what might be going on? Since nothing has changed on the warp side, could something in my payload be tripping it? (Though, I can't think of anything I changed that could have caused it to drop dead so suddenly)
The text was updated successfully, but these errors were encountered: