-
Notifications
You must be signed in to change notification settings - Fork 220
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
failed to create /run/.toolboxenv #281
Comments
I don't think toolbox currently works OOTB with any other images than fedora-toolbox though icbw. |
oh right. Might be worth recommending an update to the README |
I have read comments (examples: 1, 2) suggesting it is possible to use other images; but my attempts fail with this same error, both on git clone [email protected]:containers/toolbox.git
cd toolbox
./toolbox create --image docker.io/library/debian:buster
Same command above with verbose output
I don't know what causes the |
After debugging a bit same error on different image on IRC, this error may potentially be a red herring. I would suggest doing "podman logs containername" to try to get more output. |
Thank you! Running the same commands as before, and looking at the logs, I get:
Is that where you're going with #294 ? What is the right IRC channel for this project? I might be able to help debugging. |
It's probably not right in general but Silverblue's channel is the place where I have been asking questions about Toolbox. My hunch here is the container is failing to start at all. The image in my case works when I play with it directly with podman so working hypothesis is Toolbox has some unintended expectations about what the image is supposed to look like. Yes, the PR is an example but I don't yet know if it fixes this. |
Oh, it's a different file it's failing to unlink for you than me. For me it was host.conf, for you it's hosts. I think both are optional. |
I extended |
That has cleared everything up for me. the official kali linux container doesn't come with sudo installed. |
I think that the original I'd encourage you to try Toolbox 0.0.16. |
I got this error today, after doing
I wanted to install another package after the error above and
After exiting from the toolbox and trying
I will now recreate the toolbox and try to do just |
After removing any toolbox and even removing current image, so the latest could be retrieved, I reproduced the issue as follows:
Expected output: Current output: |
Hi @Zlopez, I just tried to create a new container and follow the steps you specified but I could not reproduce the behaviour (but I did not try to pull the latest image). What version of Podman do you use? |
|
Yes, this was very likely a Podman bug, which got fixed somewhere along the way. Let's close this. |
Steps to reproduce:
The text was updated successfully, but these errors were encountered: