-
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
Implement podman update --restart #20419
Comments
Can you just use --replace and remove and recreate the container? podman update can only update the cgroup settings for the running container. The current design of Podman does not allow the modification of the core container database. |
These are postgres, mysql, & other dev-focused data-storage containers, and have the data inside the container (volume mounts on Mac are notoriously slow). AFAIK, we'd lose the data inside the containers (unless we develop tools to copy the datas out/export the dbs). So I don't think we have a very good path to One constraint we'd be fine living with, if this changes anything, is that we only want to change the RestartPolicy of stopped containers. |
@mheon thoughts? |
Same situation as #14678 - we can do this with SQLite, but not BoltDB. Good candidate for a Podman 5.1 once we deprecate Bolt? |
A friendly reminder that this issue had no activity for 30 days. |
A friendly reminder that this issue had no activity for 30 days. |
Now that we are moving to sqlite, we can recosider this, correct @mheon ? |
Yes, though I don't think we can target this at 5.0 itself. Seems like a 5.1 thing. Removing the label. |
This will be in 5.1 |
Feature request description
I'd like to be able to do similar to Docker, and update the RestartPolicy for a container.
Suggest potential solution
On the Docker CLI, I can do
docker update --restart=never wonderous_wozniak
.Trying to do similar in podman results in:
Have you considered any alternatives?
Unknown.
Additional context
This is extra troublesome because
unless-stopped
restart policy doesnt work (#20418), and doing a naive solution likealways
does results in multiple containers each trying to start & grab the same ports on our machine. We would like to at least be able to tell some containers to stop restarting, but found thatupdate
lacks a--restart
like Docker does.The text was updated successfully, but these errors were encountered: