Closed mmmommm closed 4 months ago
Hi @mmmommm - thank you for the issue and subsequent pull request - I apologize for the lack of response.
Since we're talking only about the KIP image and assuming it would make on-going maintenance easier over installing an explicit version of crictl, I'd be in favor of moving to Debian 12 instead (as I believe you prefer). Would you mind pivoting to that approach?
@kevin-bates
Thank you for your response.
I'd be in favor of moving to Debian 12 instead
Of course, I agree with pivoting this pr to move to Debian 12 👍
It seems the operation is working without any issues.
$ cd ./etc/docker/kernel-image-puller
$ docker build -t kernel-image-puller .
[+] Building 54.8s (25/25) FINISHED
####################### Responses for command execution are being truncated.
$ docker run -d --name kip kernel-image-puller&& docker exec kip crictl -v
0d426a1de30e7cf6814f5266e23a88efc7132b7d5732cb0894c9592019be738a
crictl version v1.26.0
Congrats on your first merged pull request in this project! :tada:
Thank you for contributing, we are very proud of you! :heart:
@kevin-bates I have a question, when do you think we will be able to use the fixed image?
relate: https://github.com/jupyter-server/enterprise_gateway/issues/1363
This is Independently upgrade cri-tools to v1.24.0 or higher solution.