kata-irc-bot | <bergwolf> what is the plan for kata cli in 2.0? Samuel was talking about dropping it in one of the AC meetings. Not sure if any decision was taken | 01:27 |
---|---|---|
*** sameo has joined #kata-general | 05:09 | |
*** sgarzare has joined #kata-general | 06:38 | |
*** sameo_ has joined #kata-general | 06:43 | |
*** sameo has quit IRC | 06:43 | |
*** sameo_ has quit IRC | 07:31 | |
*** sameo_ has joined #kata-general | 07:46 | |
*** gwhaley has joined #kata-general | 08:02 | |
kata-irc-bot | <emanaricua> hello | 08:16 |
kata-irc-bot | <emanaricua> how can I add the virtio-mmio drivers to my ubuntu 20.04 to use in kata-fc? | 08:16 |
kata-irc-bot | <graham.whaley> @sunny - this Zhihong Yu - https://github.com/tedyu - says is at RH .... @yuzhihong - can you confirm? :slightly_smiling_face: | 08:59 |
*** hashar has joined #kata-general | 09:20 | |
*** sameo_ has quit IRC | 10:49 | |
*** hashar has quit IRC | 10:50 | |
*** sameo_ has joined #kata-general | 11:02 | |
*** sameo_ has quit IRC | 12:04 | |
*** igordc has quit IRC | 12:18 | |
*** sameo has joined #kata-general | 12:31 | |
*** sameo has quit IRC | 15:20 | |
*** sameo has joined #kata-general | 15:21 | |
*** sameo_ has joined #kata-general | 15:38 | |
*** sameo has quit IRC | 15:39 | |
*** sameo_ has quit IRC | 16:10 | |
*** sameo has joined #kata-general | 16:10 | |
*** kata-irc-bot has quit IRC | 16:16 | |
*** kata-irc-bot2 has joined #kata-general | 16:16 | |
*** sgarzare has quit IRC | 16:26 | |
*** gwhaley has quit IRC | 17:04 | |
kata-irc-bot2 | <tim.epkes> I have installed docker and kata as a snap. I have docker working just fine, when I modify the config of docker to the following: ```{ "log-level": "error", "storage-driver": "overlay2", "default-runtime": "kata-runtime", "runtimes": { "kata-runtime": { "path": "/snap/bin/kata-containers.runtime" } } }``` I restart docker snap and then try to execute a docker run and get the following ```$ docker | 20:10 |
kata-irc-bot2 | run --name some-redis -d redis 67dc866f49b44a6aa81c3619fa084b0848df05d0dd0177a39d86e195d7246ab2 docker: Error response from daemon: OCI runtime create failed: unable to retrieve OCI runtime error (open /var/snap/docker/423/run/docker/containerd/daemon/io.containerd.runtime.v1.linux/moby/67dc866f49b44a6aa81c3619fa084b0848df05d0dd0177a39d86e195d7246ab2/log.json: no such file or directory): fork/exec /snap/bin/kata-containers.runtime: permission | 20:10 |
kata-irc-bot2 | denied: unknown.``` I have looked and noticed some presteps which yields the same result, but here were the pre-steps ```$ sudo mkdir -p /etc/kata-containers $ sudo cp /snap/kata-containers/current/usr/share/defaults/kata-containers/configuration.toml /etc/kata-containers/ $ $EDITOR /etc/kata-containers/configuration.toml``` I didn't really see anything that I needed or was advised to edit. Also, paths seemed right. Any thoughts? | 20:10 |
kata-irc-bot2 | <tim.epkes> Ok fixed the issue. For anybody that runs into this with snap, reading the error and then going into the /var/snap/docker... you get stopped at containerd cause it is owned by root from there down (that isn't great). So the fix was ```/var/snap/docker/423/run/docker$ sudo chgrp -R docker *``` | 20:46 |
kata-irc-bot2 | <tim.epkes> and whalla it works | 20:46 |
kata-irc-bot2 | <tim.epkes> I still get a permissions error, I did have to do ```/var/snap/docker/423/run/docker$ sudo chmod -R 770 containerd``` But there is a dynamic directory that gets created an a log from there ```67dc866f49b44a6aa81c3619fa084b0848df05d0dd0177a39d86e195d7246ab2/log.json``` and the permissions on that dynamically created dir then go to root. So this causes an issue when the log.json has to be created. This is only a problem when kata | 22:56 |
kata-irc-bot2 | as a runtime is configured, if I remove kata, all is good in the world | 22:56 |
kata-irc-bot2 | <tim.epkes> so the issue is still open if somebody can assist | 22:57 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!