Deprecate all toolbox containers that don't use a reflexive entry point#336
Merged
debarshiray merged 1 commit intocontainers:masterfrom Nov 20, 2019
Conversation
debarshiray
added a commit
to debarshiray/toolbox
that referenced
this pull request
Nov 19, 2019
Toolbox containers created prior to commit 8b84b5e didn't use 'toolbox init-container' as their entry points. This prevents the container from being configured at runtime through the entry point. Being able to configure a toolbox container at runtime through the entry point is very handy, as compared to doing it statically via 'podman create', because the configuration doesn't get permanently baked into the container's definition. Instead, it's codified in toolbox(1), which can be updated over time, and the container reconfigured everytime it's started. A deprecation notice is the precursor to actually dropping support for these old containers in the future. containers#336
debarshiray
force-pushed
the
wip/rishi/deprecate-pre-toolbox-entry-point
branch
from
68031f2 to
163a950
Compare
Toolbox containers created prior to commit 8b84b5e didn't use 'toolbox init-container' as their entry points. This prevents them from being configured at runtime through the entry points. Being able to configure a toolbox container at runtime through the entry point is very handy, as compared to doing it statically via 'podman create', because the configuration doesn't get permanently baked into the container's definition. Instead, it's codified in toolbox(1), which can be updated over time, and the container reconfigured everytime it's started. A deprecation notice is the precursor to actually dropping support for these old containers in the future. Preliminary testing suggests that toolbox containers created prior to commit 8b84b5e already don't start on cgroups v2 systems. So, this is mainly targetted at cgroups v1 users, who are still able to work with those old containers. containers#336
debarshiray
force-pushed
the
wip/rishi/deprecate-pre-toolbox-entry-point
branch
from
163a950 to
9dc5281
Compare
debarshiray
pushed a commit
to debarshiray/toolbox
that referenced
this pull request
Jan 22, 2021
Ever since version 0.0.10, all newly created toolbox containers use a reflexive entry point [1] and don't need a user-specific customized image. Older containers that don't use a reflexive entry point were deprecated in version 0.0.17 [2], and aren't even supported in the Go implementation. Therefore, it's time to finally update the manuals to document the current way of doing things. Since the reflexive entry point is a key feature of toolbox containers, some text was added to explain why it's necessary and what it does. [1] Commit 8b84b5e containers#160 [2] Commit 9dc5281 containers#336
debarshiray
pushed a commit
to debarshiray/toolbox
that referenced
this pull request
Jan 22, 2021
Ever since version 0.0.10, all newly created toolbox containers use a reflexive entry point [1] and don't need a user-specific customized image. Older containers that don't use a reflexive entry point were deprecated in version 0.0.17 [2], and aren't even supported in the Go implementation. Therefore, it's time to finally update the manuals to document the current way of doing things. Since the reflexive entry point is a key feature of toolbox containers, some text was added to explain why it's necessary and what it does. [1] Commit 8b84b5e containers#160 [2] Commit 9dc5281 containers#336 containers#677
debarshiray
pushed a commit
to DaliborKr/toolbox
that referenced
this pull request
Sep 10, 2025
Starting from Toolbx 0.0.97, released in November 2020, Toolbx containers no longer need the org.freedesktop.Flatpak.SessionHelper D-Bus interface. This change was made to enable running toolbox(1) as root [1]. It is going to be five years in a few months, since this change was made, and it's becoming harder and harder to practically test backwards compatibility with these containers. All the host operating systems where Toolbx is regularly tested offer newer versions: * Arch Linux and Fedora offer the latest upstream releases * RHEL 8.10 offers at least 0.0.99.4 * Ubuntu offers at least 0.0.99.2 [2] Therefore, this is a good time to mark these older containers as deprecated, as has been done in the past in similar cases [3]. A deprecation notice is the precursor to actually dropping support for these old containers in the future. [1] Commit 71b5c8c containers@71b5c8c0a235249b containers#591 containers#267 [2] https://packages.ubuntu.com/jammy/podman-toolbox [3] Commit 9dc5281 containers@9dc52814301c5a3f containers#336 containers#1684
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Toolbox containers created prior to commit 8b84b5e didn't use
'toolbox init-container' as their entry points. This prevents the
container from being configured at runtime through the entry point.
Being able to configure a toolbox container at runtime through the
entry point is very handy, as compared to doing it statically via
'podman create', because the configuration doesn't get permanently
baked into the container's definition. Instead, it's codified in
toolbox(1), which can be updated over time, and the container
reconfigured everytime it's started.
A deprecation notice is the precursor to actually dropping support for
these old containers in the future.