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

[Error] /usr/bin/distrobox-enter: eval: line 352: syntax error near unexpected token `;' #268

Closed
AdamIsrael opened this issue May 13, 2022 · 4 comments
Labels
bug Something isn't working

Comments

@AdamIsrael
Copy link
Contributor

Describe the bug

Attempting to run distrobox-enter results in a syntax error

To Reproduce

distrobox-enter -n fedora-toolbox-36
distrobox-enter

Expected behavior

Distrobox should enter the container.

Logs
distrobox-error.log
podman.log

Desktop (please complete the following information):

  • OS: Fedora Silverblue
  • Version 36

Additional context

Running distrobox 1.2.15 installed via RPM

@AdamIsrael AdamIsrael added the bug Something isn't working label May 13, 2022
@89luca89
Copy link
Owner

Hi @AdamIsrael can you check if latest git version shows the same error?
Thanks

@89luca89
Copy link
Owner

NVM @AdamIsrael I can reproduce this

It is because the container does not have some stuff in the environment, next commit will fix this

Now what I think about it, it shouldn't happen that you do not have these variables declared inside the container creation, are you sure you're starting a distrobox container, and not a toolbx container?

I ask because the default name (fedora-toolbox-35) is the same for both!

89luca89 added a commit that referenced this issue May 13, 2022
Signed-off-by: 89luca89 <luca.dimaio1@gmail.com>
@AdamIsrael
Copy link
Contributor Author

Hi @89luca89. You're right; I had created fedora-toolbox-35 with toolbx, not distrobox. I deleted the container, recreated it with distrobox, and now it works. I hadn't realized that they wouldn't work interchangeably.

Thanks!

@89luca89
Copy link
Owner

Good to know, fixed this bug anyway 😄 thanks for the report, closing now

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