#41

Nice, you are right it is working again, though I do still get a group ID error when I create the toolbox. Thanks @jakfrost!

#42

sorry to bump and old thread, but this issue is occurring on my laptop, I have a fresh install of fedora-silverblue 33 with terminology installed via rpm-ostree. I am running in a standard user account and am able to enter and exit the toolbox until I run ‘sudo dnf install podman’, at which point I get the error:
Error: failed to inspect entry point of container fedora-toolbox-33
when trying to enter the toolbox.

#43

Did you try rebooting, it worked for me the last N times I tried since this post.

#44

Figured I’d bump this as well, I’m on a fresh Silverblue 33 install:

[agd@enoch ~]$ toolbox create test
Image required to create toolbox container.
Download registry.fedoraproject.org/f33/fedora-toolbox:33 (500MB)? [y/N]: y
Created container: test
Enter with: toolbox enter test
[agd@enoch ~]$ toolbox enter test
Error: failed to initialize container test
[agd@enoch ~]$ toolbox enter test -v
DEBU Running as real user ID 1000                 
DEBU Resolved absolute path to the executable as /usr/bin/toolbox 
DEBU Running on a cgroups v2 host                 
DEBU Checking if /etc/subgid and /etc/subuid have entries for user agd 
DEBU TOOLBOX_PATH is /usr/bin/toolbox             
DEBU Toolbox config directory is /var/home/agd/.config/toolbox 
DEBU Current Podman version is 2.2.1              
DEBU Creating runtime directory /run/user/1000/toolbox 
DEBU Old Podman version is 2.2.1                  
DEBU Migration not needed: Podman version 2.2.1 is unchanged 
DEBU Resolving container and image names          
DEBU Container: 'test'                            
DEBU Distribution: ''                             
DEBU Image: ''                                    
DEBU Release: ''                                  
DEBU Resolved container and image names           
DEBU Container: 'test'                            
DEBU Image: 'fedora-toolbox:33'                   
DEBU Release: '33'                                
DEBU Checking if container test exists            
DEBU Inspecting mounts of container test          
DEBU Starting container test                      
DEBU Inspecting entry point of container test     
DEBU Entry point PID is a float64                 
DEBU Entry point of container test is toolbox (PID=27771) 
DEBU Waiting for container test to finish initializing 
DEBU Creating runtime directory /run/user/1000/toolbox 
DEBU Checking if initialization stamp /run/user/1000/toolbox/container-initialized-27771 exists 
Error: failed to initialize container test

I’m not sure what I should be doing to debug here. I’ve been on Silverblue 33 for a couple weeks (updating each day) and it’s still persisting as a problem.

podman-2.2.1-1.fc33.x86_64
podman-plugins-2.2.1-1.fc33.x86_64

#45

Hello @storrgie ,
I am also on F33SB, and tried to create and enter a container just now with toolbox, and it works for me. Perhaps, if you don’t have an attachment to the containers you have in use you could do a podman prune I guess. What does toolbox list give you, or podman ps -a? It sounds like you maybe aren’t getting the container initialized.

#46

Trying to show that I’m golden-pathing here, seems like it really should work. This is a completely vanilla install.

[agd@enoch ~]$ toolbox list
IMAGE ID      IMAGE NAME                                        CREATED
af1f279fed20  registry.fedoraproject.org/f33/fedora-toolbox:33  4 weeks ago

CONTAINER ID  CONTAINER NAME  CREATED         STATUS  IMAGE NAME
27bc5501ea4e  test            34 minutes ago  exited  registry.fedoraproject.org/f33/fedora-toolbox:33

[agd@enoch ~]$ podman ps
CONTAINER ID  IMAGE   COMMAND  CREATED  STATUS  PORTS   NAMES

[agd@enoch ~]$ podman ps -a
CONTAINER ID  IMAGE                                             COMMAND               CREATED         STATUS                     PORTS   NAMES
27bc5501ea4e  registry.fedoraproject.org/f33/fedora-toolbox:33  toolbox --verbose...  35 minutes ago  Exited (1) 34 minutes ago          test

[agd@enoch ~]$ podman rm 27bc5501ea4e
27bc5501ea4eb09b7a978a13419d6e72795c65ef4dee4e0b71349b418a3bc4df

[agd@enoch ~]$ podman images
REPOSITORY                                     TAG     IMAGE ID      CREATED      SIZE
registry.fedoraproject.org/f33/fedora-toolbox  33      af1f279fed20  4 weeks ago  351 MB

[agd@enoch ~]$ podman rmi af1f279fed20
Untagged: registry.fedoraproject.org/f33/fedora-toolbox:33
Deleted: af1f279fed2054ce332326bed1cd07622977feeee3925bf70a78d0514a9d714f

[agd@enoch ~]$ podman images
REPOSITORY  TAG     IMAGE ID  CREATED  SIZE

[agd@enoch ~]$ toolbox create testing
Image required to create toolbox container.
Download registry.fedoraproject.org/f33/fedora-toolbox:33 (500MB)? [y/N]: y
Created container: testing
Enter with: toolbox enter testing

[agd@enoch ~]$ toolbox enter testing -v
DEBU Running as real user ID 1000                 
DEBU Resolved absolute path to the executable as /usr/bin/toolbox 
DEBU Running on a cgroups v2 host                 
DEBU Checking if /etc/subgid and /etc/subuid have entries for user agd 
DEBU TOOLBOX_PATH is /usr/bin/toolbox             
DEBU Toolbox config directory is /var/home/agd/.config/toolbox 
DEBU Current Podman version is 2.2.1              
DEBU Creating runtime directory /run/user/1000/toolbox 
DEBU Old Podman version is 2.2.1                  
DEBU Migration not needed: Podman version 2.2.1 is unchanged 
DEBU Resolving container and image names          
DEBU Container: 'testing'                         
DEBU Distribution: ''                             
DEBU Image: ''                                    
DEBU Release: ''                                  
DEBU Resolved container and image names           
DEBU Container: 'testing'                         
DEBU Image: 'fedora-toolbox:33'                   
DEBU Release: '33'                                
DEBU Checking if container testing exists         
DEBU Inspecting mounts of container testing       
DEBU Starting container testing                   
DEBU Inspecting entry point of container testing  
DEBU Entry point PID is a float64                 
DEBU Entry point of container testing is toolbox (PID=33781) 
DEBU Waiting for container testing to finish initializing 
DEBU Creating runtime directory /run/user/1000/toolbox 
DEBU Checking if initialization stamp /run/user/1000/toolbox/container-initialized-33781 exists 
Error: failed to initialize container testing
#47

Think it may be this https://github.com/containers/toolbox/issues/687

#48

Thanks for the link, I posted a follow up there. I’d updated everything today and still see the same issue.

#49

I too cannot start my containers, again. I feel like it happens every other time I update. I wish Silverblue had some or better automated testing that would include running toolboxes as they are a key part of the workflow.
BTW. this is what openSuse Tubmleweed does, for inspiration:

1 Like