Comments (7)
i take up this issue
from checkpointctl.
Hi @Nitishupkr, you are more than welcome to work on this GitHub issue. Please let us know if you have any questions.
from checkpointctl.
@Nitishupkr you still working on this? if not then I can take on.
from checkpointctl.
@rst0git if I am not wrong then container engine store container checkpoints here -
podman - /var/lib/containers/storage/overlay-containers
CRI-O - /var/run/crio/checkpoints
for the list command are we gonna print the full path of checkpoint containers?
and is there any other directories we also need to check? and what about the checkpoints that are store in the directory specified by the users during the container checkpoint command execution?
from checkpointctl.
@Parthiba-Hazra As a starting point, we can add checkpointctl list
command that shows checkpoints stored in /var/lib/kubelet/checkpoints/
. This path is used by Kubernetes/CRI-O and contains files with the following naming convention:
checkpoint-<pod-name>_<namespace-name>-<container-name>-<timestamp>.tar
Example:
checkpoint-counter-tl58j_default-counter-2023-10-12T11:02:56+01:00.tar
for the list command are we gonna print the full path of checkpoint containers?
It would good to use file name parsing and output a table similar to the checkpointctl show
command. This functionality is particularly useful in scenarios where automated periodic checkpointing is used as a fault-tolerance mechanism, leading to many container checkpoints created in this directory.
what about the checkpoints that are store in the directory specified by the users during the container checkpoint command execution?
Once the list command has been merged, we could extend checkpointctl with support for configuration files that enable users to change the default path or to specify additional locations.
@adrianreber Do you have any thoughts?
from checkpointctl.
@Parthiba-Hazra As a starting point, we can add
checkpointctl list
command that shows checkpoints stored in/var/lib/kubelet/checkpoints/
. This path is used by Kubernetes/CRI-O and contains files with the following naming convention:checkpoint-<pod-name>_<namespace-name>-<container-name>-<timestamp>.tar
Example:
checkpoint-counter-tl58j_default-counter-2023-10-12T11:02:56+01:00.tar
for the list command are we gonna print the full path of checkpoint containers?
It would good to use file name parsing and output a table similar to the
checkpointctl show
command. This functionality is particularly useful in scenarios where automated periodic checkpointing is used as a fault-tolerance mechanism, leading to many container checkpoints created in this directory.what about the checkpoints that are store in the directory specified by the users during the container checkpoint command execution?
Once the list command has been merged, we could extend checkpointctl with support for configuration files that enable users to change the default path or to specify additional locations.
@adrianreber Do you have any thoughts?
yes that sounds good.
from checkpointctl.
Related Issues (19)
- How to install checkpointctl tool HOT 13
- Make command fails HOT 9
- Doubt - Relation with Kubernetes HOT 2
- Versioning? HOT 5
- How can I install? HOT 4
- Showing env and mounts HOT 2
- Do not unpack the whole checkpoint archive HOT 4
- Extend checkpointctl to convert checkpoint archives to OCI images HOT 2
- Add support for showing information for multiple checkpoints HOT 7
- Do not use the podman network status HOT 2
- Add integration test with podman HOT 3
- Process tree output looks not totally correct. HOT 7
- Extend the output format with a tree view HOT 1
- Extend `inspect` output format with JSON HOT 3
- Refactor `checkpointctl.go` and move commands into individual files HOT 16
- Update `README.md`
- Prune process tree by PID if specified
- Statisitics output adds `us` everywhere
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from checkpointctl.