Monday, 2022-02-14

kata-irc-bot<dgibson> is there a schedule for when 2.4alpha releases will come out?05:50
kata-irc-bot<dgibson> thanks06:56
kata-irc-bot<dgibson> so, another couple of weeks06:56
kata-irc-bot<dgibson> bother, I guess I'll need to figure out how to deploy kata from source06:56
kata-irc-bot<fidencio> if you happen to have docker installed, there's a makefile target to generate all the binaries for you in the same format that kata-deploy uses06:57
kata-irc-bot<dgibson> well, I could install docker06:58
kata-irc-bot<dgibson> I'd then need to figure out how to stage that onto my cluster06:58
kata-irc-bot<fidencio> Oh, I see.  Let me guess, you're testing with an OCP cluster.07:11
kata-irc-bot<fidencio> If so, the easiest and less traumatic way to do so is follow what the RPM does, dropping the files in the locations the RPM drops the files ...  And let the systemd service re-generate the initrd / kernel to be used by the VM07:12
kata-irc-bot<dgibson> actually no, it's plain k8s on RHEL08:22
kata-irc-bot<dgibson> Adrian set it up08:23
kata-irc-bot<dgibson> currently it has kata2.4alpha2 installed via kata-deploy08:23
kata-irc-bot<dgibson> but I need to update to something with the bugfix I did last week08:23
kata-irc-bot<fidencio> Then you can build the binaries using `make kata-tarball`08:24
kata-irc-bot<fidencio> It'll generate a tarball with everything you need, from main.08:24
kata-irc-bot<dgibson> ok.. but how do I get them onto my cluster in usable state?08:25
kata-irc-bot<fidencio> And put it in the same location kata-deploy puts its things (which is `/opt/kata/....`08:26
kata-irc-bot<dgibson> sorry, I'm not clear on what you mean by either of those options08:26
kata-irc-bot<fidencio> Can you `ssh` into your cluster?08:26
kata-irc-bot<dgibson> oh, ok so basically just manually overwrite binaries from kata-deploy08:26
kata-irc-bot<dgibson> gross, but doable08:26
kata-irc-bot<fidencio> That's the easiest way to debug. Or you can build a new kata-deploy image, store it in your quay.io account08:26
kata-irc-bot<fidencio> And deploy it on your cluster (that would be the non-gross way)08:27
kata-irc-bot<dgibson> ok08:27
kata-irc-bot<dgibson> how would I do that?08:27
kata-irc-bot<fidencio> https://github.com/kata-containers/kata-containers/blob/cf53ec2c714d3dd665806c07d92120ae869f1573/.github/workflows/release.yaml#L80-L8508:28
kata-irc-bot<fidencio> From the moment you have the binary, you can follow the instructions in that action (mind, change the quay.io to your quay.io account / space)08:28
kata-irc-bot<dgibson> sure..08:29
kata-irc-bot<dgibson> does that generate the yaml I need somewhere?08:29
kata-irc-bot<fidencio> No, you'll have to change this line to point to your own quay.io repo: https://github.com/kata-containers/kata-containers/blob/cf53ec2c714d3dd665806c07d9[…]3/tools/packaging/kata-deploy/kata-deploy/base/kata-deploy.yaml08:30
kata-irc-bot<fidencio> (and do the same one on kata-cleanup yaml as well)08:30
kata-irc-bot<dgibson> hm, ok08:31
kata-irc-bot<dgibson> too dang many steps, but what's new08:31
kata-irc-bot<dgibson> thanks for the info08:32
kata-irc-bot<fidencio> No problem, David, hope that helps.08:32
kata-irc-bot<dgibson> hrm09:19
kata-irc-bot<dgibson> make kata-tarball has failed cryptically :(09:19
kata-irc-bot<fidencio> How?09:20
kata-irc-bot<dgibson> ```+ sh -c DEBIAN_FRONTEND=noninteractive apt-get install -y -qq docker-ce-rootless-extras >/dev/null debconf: delaying package configuration, since apt-utils is not installed debconf: delaying package configuration, since apt-utils is not installed New password: Password change aborted. passwd: Authentication token manipulation error passwd: password unchanged Use of uninitialized value $answer in chop at /usr/sbin/adduser line 591. Use09:21
kata-irc-botof uninitialized value $answer in pattern match (m//) at /usr/sbin/adduser line 592. Use of uninitialized value $answer in chop at /usr/sbin/adduser line 621. Use of uninitialized value $answer in pattern match (m//) at /usr/sbin/adduser line 622. debconf: delaying package configuration, since apt-utils is not installed New password: Password change aborted. passwd: Authentication token manipulation error passwd: password unchanged Use of09:21
kata-irc-botuninitialized value $answer in chop at /usr/sbin/adduser line 591. Use of uninitialized value $answer in pattern match (m//) at /usr/sbin/adduser line 592. New password: Password change aborted. passwd: Authentication token manipulation error passwd: password unchanged Use of uninitialized value $answer in chop at /usr/sbin/adduser line 591. Use of uninitialized value $answer in pattern match (m//) at /usr/sbin/adduser line 592. Use of09:21
kata-irc-botuninitialized value $answer in chop at /usr/sbin/adduser line 621. Use of uninitialized value $answer in pattern match (m//) at /usr/sbin/adduser line 622. Use of uninitialized value $answer in chop at /usr/sbin/adduser line 621. Use of uninitialized value $answer in pattern match (m//) at /usr/sbin/adduser line 622. New password: Password change aborted. passwd: Authentication token manipulation error passwd: password unchanged Use of09:21
kata-irc-botuninitialized value $answer in chop at /usr/sbin/adduser line 591. Use of uninitialized value $answer in pattern match (m//) at /usr/sbin/adduser line 592. Use of uninitialized value $answer in chop at /usr/sbin/adduser line 621. Use of uninitialized value $answer in pattern match (m//) at /usr/sbin/adduser line 622. New password: Password change aborted. passwd: Authentication token manipulation error passwd: password unchanged Use of09:21
kata-irc-botuninitialized value $answer in chop at /usr/sbin/adduser line 591. Use of uninitialized value $answer in pattern match (m//) at /usr/sbin/adduser line 592. Use of uninitialized value $answer in chop at /usr/sbin/adduser line 621. Use of uninitialized value $answer in pattern match (m//) at /usr/sbin/adduser line 622. debconf: delaying package configuration, since apt-utils is not installed debconf: delaying package configuration, since apt-utils09:21
kata-irc-botis not installed debconf: delaying package configuration, since apt-utils is not installed debconf: delaying package configuration, since apt-utils is not installed ba38ac6a7431726cd869a219579c3552e0092e7e7f2e1ba328d2761c466d7128 Error: statfs /var/run/docker.sock: permission denied make[2]: *** [tools/packaging/kata-deploy/local-build/Makefile:30: firecracker-tarball-build] Error 125 make[2]: Leaving directory '/home/dwg/src/kata-containers'09:21
kata-irc-botmake[1]: *** [/home/dwg/src/kata-containers/tools/packaging/kata-deploy/local-build/Makefile:36: firecracker-tarball] Error 2 make[1]: *** Waiting for unfinished jobs....```09:21
kata-irc-bot<fidencio> Let me run it locally here and see if I face the same issue.09:22
kata-irc-bot<fidencio> I'm assuming you're using *docker* and not *podman*. Right?09:22
kata-irc-bot<dgibson> no, it is podman09:24
kata-irc-bot<dgibson> it's a fedora host09:24
kata-irc-bot<dgibson> but the errors there appear to be running docker within another container09:25
kata-irc-bot<fidencio> The script is docker specific so far, and that's the reason I mentioned "if you happen to have docker installed ..."09:26
kata-irc-bot<dgibson> urgh09:26
kata-irc-bot<fidencio> Feel free to submit patches adding support for docker.09:26
kata-irc-bot<dgibson> do you know what's docker specific about it?09:26
kata-irc-bot<fidencio> To start with: ```docker run ${TTY_OPT} \         -v /var/run/docker.sock:/var/run/docker.sock \```09:27
kata-irc-bot<fidencio> That's from `kata-deploy-binaries-in-docker.sh`09:27
kata-irc-bot<fidencio> Hmm. Then I am not really sure. :slightly_smiling_face:09:28
kata-irc-bot<fidencio> It was not written as a "docker specific thing", but I don't think it was ever tested with "podman"09:29
kata-irc-bot<fidencio> Anyways, I'd recommend you to sync with @ssheribe as, maybe, the build script is the least of your problems for running this on a RHEL right now09:30
kata-irc-bot<ssheribe> @fidencio, @samuel.ortiz , FYI, @wmoschet have tested main on ubuntu vm (using vagrant) and also got frozen. oddly nothing seems to fail when the VM is on azure, something with certain network device? IDK09:30
kata-irc-bot<dgibson> I'm not running on rhel09:31
kata-irc-bot<dgibson> not the buld, that is09:31
kata-irc-bot<dgibson> I will be deploying on rhel later09:31
kata-irc-bot<samuel.ortiz> @ssheribe @wmoschet I did not have time to look at that on Friday. Could you please open an issue for that?09:32
kata-irc-bot<ssheribe> Unfortunately I'd also go for binaries copy, although it's indeed ugly09:38
kata-irc-bot<ssheribe> Also i think if you'll comment /test_kata_deploy on your PR it will generate the tarball for you , i think, @fidencio no?09:40
kata-irc-bot<fidencio> Oh, that's correct, that can be a nice way to do so.09:40
kata-irc-bot<fidencio> But that's a quite expensive way to do so (for the kata-containers community)09:40
kata-irc-bot<dgibson> right, and slow for me too09:41
kata-irc-bot<dgibson> in any case the PR is merged already09:41
kata-irc-bot<fidencio> With this in mind, I think we can have a hook on merge to generate a quay.io kata-deploy image on every merged PR09:41
kata-irc-bot<wmoschet> yep, on Friday I could reproduce it with vagrant as well.12:48

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!