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

packer command not working #144

Open
jramhani opened this issue Jul 19, 2024 · 2 comments
Open

packer command not working #144

jramhani opened this issue Jul 19, 2024 · 2 comments
Assignees
Labels
failure Issue found in production while not necessarily being a mistake

Comments

@jramhani
Copy link
Contributor

All packers

packer amber example.exe

00:00:00.586 [ERROR] [Errno 2] No such file or directory: 'amber'

UPX works

packer upx example.exe

@dhondta dhondta added the failure Issue found in production while not necessarily being a mistake label Jul 19, 2024
@dhondta dhondta self-assigned this Jul 19, 2024
@dhondta
Copy link
Collaborator

dhondta commented Jul 19, 2024

@jramhani Thank you for reporting.
Actually, this is not a bug but a misleading error message because of the context ;

  • When you install the box, setup of some items (including packers) may fail without a warning.
  • This means that, when you use the related tool (in this case packer), it will raise a OSError as it does not find the item to be run (amber).

So please try the following and tell if the setup succeeds ;

$ packing-box setup packer amber

@jramhani
Copy link
Contributor Author

Oh, okey thanks clarification;

I tried to setup using the command mentioned but got the following error :

00:00:00.108 [INFO] Setting up Amber...
00:00:02.610 [ERROR] mv: cannot move '/home/user/.opt/packers' to a subdirectory of itself, '/home/user/.opt/packers/amber'
00:00:02.610 [CRITICAL] Last command's result does not exist (/home/user/.opt/packers/amber) ; current: {'ln': 'amber'}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
failure Issue found in production while not necessarily being a mistake
Projects
None yet
Development

No branches or pull requests

2 participants