-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Remove rkt container runtime #3906
Comments
Reference #168
And #571 (for ISO)
Ping @tstromberg |
Let's nuke rkt. |
Related: #3920 |
One quirk: the |
@tstromberg : yeah, I saw that. Maybe upstream has some kind of workaround for it, will peek around. https://github.com/coreos/toolbox
|
Deleted the toolbox for now, seems like running containers with podman isn't working at the moment. _ _
_ _ ( ) ( )
___ ___ (_) ___ (_)| |/') _ _ | |_ __
/' _ ` _ `\| |/' _ `\| || , < ( ) ( )| '_`\ /'__`\
| ( ) ( ) || || ( ) || || |\`\ | (_) || |_) )( ___/
(_) (_) (_)(_)(_) (_)(_)(_) (_)`\___/'(_,__/'`\____)
$ sudo podman pull busybox
Trying to pull docker.io/busybox:latest...Getting image source signatures
Copying blob 697743189b6d: 738.18 KiB / 738.18 KiB [========================] 1s
Copying config d8233ab899d4: 1.46 KiB / 1.46 KiB [==========================] 0s
Writing manifest to image destination
Storing signatures
d8233ab899d419c58cf3634c0df54ff5d8acc28f8173f09c21df4a07229e1205
$ sudo podman run -it busybox
error configuring network namespace for container b731699b47263152e29888a9b91d671346548c0d059ec056a8aa8ce1797077d6: Missing CNI default network Probably needs some CNI configuration. |
Found a way to use podman for the extraction, but still use systemd-nspawn for running. |
Can this be closed? |
Closed in 1.0. |
While the
rkt
component of kubernetes that was added in 1.3 and removed in 1.9 is gone,there is a CRI replacement called
rktlet
. But even that is also stuck in the 1.8 - 1.11 era ?So it seems like there is not too much development going on with
rkt
, and nobody using it.Users looking for a supported alternative container runtime would be better off with
cri-o
...Therefore the suggestion is to remove it, for 1.0:
master...afbjorklund:rkt-remove
I made a small effort to update it, in case I am wrong:
master...afbjorklund:rktlet
The text was updated successfully, but these errors were encountered: