-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[FEATURE REQUEST]: container update for compat endpoint #14678
Comments
The architecture of Podman continues to prevent implementation of this functionality - we can't alter containers after creation. We were able to add the ability to make small changes (e.g. renaming, adding network aliases) but these changes were very difficult, and there's no real way to generalize them. |
A friendly reminder that this issue had no activity for 30 days. |
A friendly reminder that this issue had no activity for 30 days. |
A friendly reminder that this issue had no activity for 30 days. |
@mheon sounds like a can't fix? |
We are discussing a major rewrite of the DB backend. If we're going to do that, might as well look into whether we can make this possible as part of it. I'll throw it in the bucket of issues we know we want fixed with the new DB, like making pod and container names no longer conflict. |
great idea, thanks, Matt! |
The update method in libpod api also respond with 404: |
Once we can implement the backend fully, we can enable the API. |
@mheon still planned? |
This is possible with SQLite, but not Bolt, so I think we want to hold off
until we deprecate Bolt so we don’t end up with a command that only works
with one DB type that is also a fully supported DB
…On Thu, Oct 19, 2023 at 05:29 Valentin Rothberg ***@***.***> wrote:
@mheon <https://github.com/mheon> still planned?
—
Reply to this email directly, view it on GitHub
<#14678 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB3AOCGGIEIK4D5PEIHMLWTYADXH5AVCNFSM5ZLYMFQKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCNZXGA2DENBTGY2Q>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Hey, I am not sure if its a bug or a feature request, but Podman does not provide container update operation for compat endpoint, see https://docs.docker.com/engine/api/v1.41/#operation/ContainerUpdate
Use case:
Related: #5763
Thanks
The text was updated successfully, but these errors were encountered: