| *** pmannidi is now known as pmannidi|AFK | 01:17 | |
| *** pmannidi|AFK is now known as pmannidi | 02:22 | |
| *** pmannidi is now known as pmannidi|brb | 05:17 | |
| *** pmannidi|brb is now known as pmannidi|Lunch | 05:22 | |
| *** pmannidi|Lunch is now known as pmannidi | 06:20 | |
| digitalsimboja | Morning all! maysams, ltomasbo: I have been stuck here since while setting up virtualbox | 08:23 |
|---|---|---|
| digitalsimboja | https://paste.opendev.org/show/809488/ | 08:23 |
| digitalsimboja | Please assist | 08:23 |
| digitalsimboja | Thanks | 08:23 |
| dulek | Try running `apt install docker-ce` and show the results. | 09:39 |
| digitalsimboja | hello | 10:21 |
| maysams | digitalsimboja: Hi | 10:25 |
| maysams | dulek has suggested the following: | 10:25 |
| maysams | Try running `apt install docker-ce` and show the results. | 10:25 |
| digitalsimboja | ok | 10:29 |
| digitalsimboja | I am getting this: https://paste.opendev.org/show/809492/ | 11:33 |
| dulek | It's suggesting to run `systemctl status devstack@etcd.service" and "journalctl -xe"` to get more info. | 13:58 |
| digitalsimboja | hi dulek, I have installed docker-ce as you suggested. I am still getting stuck here: https://paste.opendev.org/show/809506/ | 14:40 |
| digitalsimboja | Does it depend on my network? | 14:40 |
| digitalsimboja | https://paste.opendev.org/show/809507/ | 14:42 |
| dulek | digitalsimboja: `sudo journalctl -u docker` can help. | 14:44 |
| dulek | digitalsimboja: But in general it seems to fail on package configuration. | 14:44 |
| dulek | digitalsimboja: Ah yeah, it haven't started it on installation, I see. So that journalctl can help us. | 14:45 |
| digitalsimboja | https://paste.opendev.org/show/809508/ | 14:46 |
| dulek | digitalsimboja: What Ubuntu is that? | 14:49 |
| dulek | Focal, okay. | 14:50 |
| dulek | It should work. | 14:50 |
| dulek | digitalsimboja: I see in https://forums.docker.com/t/failed-to-load-listeners-no-sockets-found-via-socket-activation-make-sure-the-service-was-started-by-systemd/62505/2 that you got to set `unix://` instead of `fd://` in sudo systemctl edit docker.service. | 14:51 |
| dulek | A bit weird to me, but worth a shot. | 14:51 |
| digitalsimboja | checking | 14:52 |
| dulek | digitalsimboja: Ah, looks like you can just run `sudo /usr/bin/dockerd -H unix:// --containerd=/run/containerd/containerd.sock`, stop and retry starting the service with `sudo systemctl start docker` | 14:52 |
| digitalsimboja | on it | 14:54 |
| digitalsimboja | lets hope this run succeeds | 14:59 |
| digitalsimboja | Ooops dulek, a different fail point: https://paste.opendev.org/show/809509/ | 15:00 |
| dulek | digitalsimboja: Line 23 of that paste tells you what to do to get info. | 15:01 |
| digitalsimboja | https://paste.opendev.org/show/809510/ | 15:02 |
| digitalsimboja | ^ | 15:02 |
| dulek | digitalsimboja: You're rerunning stack.sh without unstack.sh, are you? | 15:02 |
| digitalsimboja | ohh that is correct. my mistake right there | 15:05 |
| dulek | digitalsimboja: Yeah, it's not designed for that. You got to unstack.sh first to close all the apps that it already started - otherwise the ports or sockets might already be created, causing problems. | 15:14 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!