In order to examine how to use containers for development, I ran across this link:
If I follow the instructions there, everything works as described on Silverblue, but when I try it on Fedora workstation (30 in both cases), toolbox cannot start the default container, but I can build it with podman. But then I can’t get the gedit in the container to work, while it works flawlessly in Silverblue. Anybody know what is going on here? Toolbox is documented as working just as well on workstation as on Silverblue.
On workstation 30, toolbox clains it successfully created the container, but
> mike@lenny ~]$ toolbox -v enter toolbox: resolved absolute path for /usr/bin/toolbox to /usr/bin/toolbox toolbox: TOOLBOX_PATH is /usr/bin/toolbox toolbox: checking if 'podman system migrate' exists toolbox: migration not needed: 1.3.1 is unchanged toolbox: Fedora generational core is f30 toolbox: base image is fedora-toolbox:30 toolbox: container is fedora-toolbox-30 toolbox: checking if container fedora-toolbox-30 exists toolbox: trying to start container fedora-toolbox-30 Error: unable to start container "fedora-toolbox-30": container create failed: time="2019-06-05T23:53:07-04:00" level=fatal msg="try_mapping_tool:243 nsenter: mapping tool not present: Operation not permitted" time="2019-06-05T23:53:07-04:00" level=fatal msg="nsexec:892 nsenter: failed to sync with parent: read(SYNC_USERMAP_ACK): Invalid argument" time="2019-06-05T23:53:07-04:00" level=warning msg="no such directory for freezer.state" time="2019-06-05T23:53:07-04:00" level=warning msg="no such directory for freezer.state" time="2019-06-05T23:53:07-04:00" level=error msg="container_linux.go:346: starting container process caused \"process_linux.go:319: getting the final child's pid from pipe caused \\\"EOF\\\"\"\n" container_linux.go:346: starting container process caused "process_linux.go:319: getting the final child's pid from pipe caused \"EOF\"" : internal libpod error toolbox: failed to start container fedora-toolbox-30 >