[00:14] *** step has joined #warrior
[00:16] *** zhongfu has joined #warrior
[00:16] *** nepeat has joined #warrior
[00:18] *** pinkieval has joined #warrior
[06:24] *** fennec has quit IRC (Read error: Operation timed out)
[06:39] *** colona has joined #warrior
[06:40] *** colona_ has quit IRC (Ping timeout: 857 seconds)
[06:41] *** fennec has joined #warrior
[13:57] *** bsmith093 has quit IRC (Read error: Operation timed out)
[14:14] *** bsmith093 has joined #warrior
[15:08] *** Craigle has quit IRC (Quit: The Lounge - https://thelounge.chat)
[15:38] *** Craigle has joined #warrior
[18:28] <chfoo> anyone might have an idea on why docker doesn't start up in the virtual machine? https://github.com/ArchiveTeam/Ubuntu-Warrior/issues/8
[19:17] *** Dj-Wawa has quit IRC (Quit: Dj-Wawa)
[19:18] *** Dj-Wawa has joined #warrior
[19:38] *** Dj-Wawa has quit IRC (Quit: Dj-Wawa)
[19:38] *** Dj-Wawa has joined #warrior
[19:45] <prq> chfoo docker itself has logs that could explain why it can't start up. I haven't done much with the ubuntu warrior appliance, but it's just in journald: journalctl -u docker.service
[19:45] <prq> that usually has some good info to go on
[19:53] <chfoo> i just checked and the appliance doesn't use systemd 
[19:53] <chfoo> it runs alpine linux so i'm not familiar where they can check for logging
[21:03] <prq> on alpine, docker logs to /var/log/docker.log
[21:06] <prq> rc script is at /etc/init.d/docker and /etc/conf.d/docker are the relevant init system scripts for it. In particular, you can edit /etc/conf.d/docker and set DOCKER_OPTS="--debug" and restart the docker service in order to get debug level logging out to /var/log/docker.log