#warrior 2019-12-14,Sat

↑back Search

Time Nickname Message
00:21 πŸ”— jesse-s has quit IRC (Ping timeout: 1230 seconds)
00:22 πŸ”— jesse-s has joined #warrior
00:29 πŸ”— atbk_ has quit IRC (Ping timeout: 745 seconds)
00:58 πŸ”— oshura_ Hey Wingy, I think we gave my pi a stroke lol
01:10 πŸ”— oshura_ I think two instances might have been too much
01:17 πŸ”— oshura_ I'm pretty sure the containers are running but I have no earthly idea if it's working. Earlier it wouldn't work because it ran out of ram
01:25 πŸ”— britmob has quit IRC (Read error: Connection reset by peer)
02:14 πŸ”— Wingy has joined #warrior
02:15 πŸ”— Wingy oshura_: Sorry if I missed anything, irc connection died while I was away
02:19 πŸ”— Wingy4 has joined #warrior
02:19 πŸ”— Wingy has quit IRC (Read error: Operation timed out)
02:19 πŸ”— Wingy4 is now known as Wingy
02:23 πŸ”— Wingy9 has joined #warrior
02:24 πŸ”— Wingy has quit IRC (Read error: Operation timed out)
02:24 πŸ”— Wingy9 is now known as Wingy
02:27 πŸ”— Wingy has quit IRC (Read error: Operation timed out)
02:28 πŸ”— oshura_ No worries
02:28 πŸ”— oshura_ <oshura_> Hey Wingy, I think we gave my pi a stroke lol
02:28 πŸ”— oshura_ <oshura_> I think two instances might have been too much
02:28 πŸ”— oshura_ <oshura_> I'm pretty sure the containers are running but I have no earthly idea if it's working. Earlier it wouldn't work because it ran out of ram
02:30 πŸ”— oshura_ ^ that's all you missed
02:31 πŸ”— oshura_ oh, he fell out again...
02:43 πŸ”— d5f4a3622 has quit IRC (Ping timeout: 248 seconds)
03:10 πŸ”— Wingy has joined #warrior
03:33 πŸ”— d5f4a3622 has joined #warrior
04:10 πŸ”— DogsRNice has quit IRC (Read error: Connection reset by peer)
04:16 πŸ”— Wingy has quit IRC (Read error: Operation timed out)
05:36 πŸ”— atbk has joined #warrior
09:35 πŸ”— mls has quit IRC (Ping timeout: 258 seconds)
09:44 πŸ”— mls has joined #warrior
12:17 πŸ”— Flashfire has quit IRC (Remote host closed the connection)
12:17 πŸ”— kiska has quit IRC (Remote host closed the connection)
12:17 πŸ”— Flashfire has joined #warrior
12:17 πŸ”— kiska has joined #warrior
13:34 πŸ”— Wingy has joined #warrior
13:38 πŸ”— Wingy has quit IRC (Read error: Operation timed out)
14:04 πŸ”— jc86035 has quit IRC (Quit: Connection closed for inactivity)
14:12 πŸ”— TetryonBe hmm, anyone seen 'fatal error: runtime: address space conflict' on the console?
14:13 πŸ”— Kaz sounds like you're running out of memory, maybe?
14:13 πŸ”— Kaz can't say I've ever seen that error
14:14 πŸ”— TetryonBe you mean the memory allocated by VirtualBox? Possible, I left the default settings
14:14 πŸ”— Kaz yep
14:16 πŸ”— TetryonBe ok, I will increase from 400 to 800MB then. Thanks for the hint.
14:17 πŸ”— TetryonBe FWIW this was given by a go process
14:22 πŸ”— oshura_ anyone else here can help me figure out why I wouldn't be able to see the localhost warrior client on my pi from the docker image? I think I may be inputting the incorrect address in my chrome
14:30 πŸ”— Wingy has joined #warrior
14:33 πŸ”— markedL I didn't think we have any go, but could be wrong
14:34 πŸ”— Wingy has quit IRC (Read error: Operation timed out)
14:34 πŸ”— Wingy has joined #warrior
14:36 πŸ”— Wingy has quit IRC (Read error: Operation timed out)
14:37 πŸ”— Wingy has joined #warrior
14:37 πŸ”— oshura_ wingy?
14:39 πŸ”— Wingy has quit IRC (Read error: Operation timed out)
14:41 πŸ”— JAA Yeah, I'm not aware of any Go usage either. How did you get a Go process in the warrior, TetryonBe?
14:44 πŸ”— JAA Oh wait, Docker is Go, and the VM is just a wrapper around the Docker container.
14:45 πŸ”— Kaz starting to think we should just pull the VM completely now
14:45 πŸ”— Kaz guide people towards docker directly
14:45 πŸ”— oshura_ can docker be run from windows?
14:46 πŸ”— Kaz in theory, yes
14:46 πŸ”— Kaz haven't tested it
14:48 πŸ”— markedL docker runs on win, mac, and linux
14:52 πŸ”— TetryonBe JAA: no idea, didnt even try to log in to it
14:53 πŸ”— TetryonBe markedL: does it run on Win7 too? or just Win10?
14:56 πŸ”— Kaz oh yeah, this is dead simple
14:56 πŸ”— Kaz `docker run -d -p 8001:8001 archiveteam/warrior-dockerfile` is all there is to it
14:56 πŸ”— markedL https://docs.docker.com/docker-for-windows/install/#what-to-know-before-you-install
14:56 πŸ”— JAA Requires Win 10 Pro or higher according to https://docs.docker.com/docker-for-windows/install/
14:57 πŸ”— markedL https://software.intel.com/en-us/intel-system-studio-docker-install-windows
14:57 πŸ”— JAA But Win 7 support runs out in January, so...
14:58 πŸ”— TetryonBe hmm, sooner than I remembered :/
15:05 πŸ”— markedL I was going to look into WSL, there's 1 and 2 now
15:05 πŸ”— phillipsj Is docker supposed to be any easier to set up than Virtualbox?
15:06 πŸ”— phillipsj I have been thinking runing the scripts directly may be easier than setting up docker.
15:08 πŸ”— JAA For the average person running a worker, the warrior is definitely the easiest. Whether you consider Docker or scripts easier probably depends on how much you've worked with Docker before.
15:10 πŸ”— oshura_ would I be able to still see the warrior on my browser if I run the docker image directly on windows vs VM?
15:10 πŸ”— Kaz yes
15:14 πŸ”— Terbium I personally found docker easier. I was turned away when i saw the VM was the only option until a dug a little deeper and found the docker version
15:19 πŸ”— JAA Terbium: phillipsj asked about Docker vs scripts though, not Docker vs VM. The scripts are essentially another layer deeper than the Docker containers.
15:20 πŸ”— Terbium Oh
15:20 πŸ”— * phillipsj currently has VM working, but not docker.
15:22 πŸ”— markedL seems to me, Win 7 is the biggest outlier, followed by Win 10 Home
15:22 πŸ”— JAA I've never used the VM at all because it was horribly insecure when I arrived here. Set up the scripts and used that until I started focusing on other things and no longer really run the projects myself.
15:23 πŸ”— phillipsj In my seraching I found docker is currently broken on FreeBSD as well.
15:28 πŸ”— markedL docker might let us borrow other pieces from the ecosystem instead of rolling our own
15:30 πŸ”— Terbium i'm personally using Docker's scaling system so I can just tell it to setup 40 containers and it will do it. No need for a bash script. If i want to stop or delete all 40 containers, i can do it in one command. That's my personal experience at least for what its worth
15:31 πŸ”— markedL how does it stop 40 containers
15:32 πŸ”— oshura_ so it looks like to run docker on Win10 you have to have win10Pro
15:32 πŸ”— Terbium "# docker-compose down"
15:32 πŸ”— Terbium docker-compose lets me create a container stack and lets me manage them as one
15:32 πŸ”— Terbium so with "docker-compose down" i can tell it to stop or delete the entire stack however many warrior containers it has
15:33 πŸ”— Terbium of course, this scaling is simply to bypass the "6 concurrent items" limit which was placed for the VM version but carries over to the docker version
15:34 πŸ”— Terbium not sure if there is any other special reasion (besides matching the VM version of warrior) that the limit was set of 6
15:35 πŸ”— markedL what does docker-compose ps show after you run docker-compose stop
15:35 πŸ”— markedL seems like it must be a hard kill
15:36 πŸ”— Terbium that's a good question, i never really checked, lemme test it out and check the logs to see what type of kill it is
15:37 πŸ”— Wingy has joined #warrior
15:40 πŸ”— Terbium markedL: "archiveteam/warrior-dockerfile "/sbin/my_init" About a minute ago Exited (2) 21 seconds ago "
15:41 πŸ”— Terbium from "docker ps -a"
15:41 πŸ”— Terbium seems like a hard kill
15:41 πŸ”— Wingy has quit IRC (Read error: Operation timed out)
15:41 πŸ”— Terbium "Killing all processes..."
15:42 πŸ”— Terbium i'm guessing the dockerfil doesnt have graceful shutdown implemented possibly
15:42 πŸ”— Terbium dockerfile*
16:02 πŸ”— Kaz Terbium: this is a bad idea, in general
16:03 πŸ”— Kaz we've seen lots of issues with people that spin up loads of warriors, then suddenly they all fall over when we need to have them work on a heavy project
16:03 πŸ”— Kaz if there's a specific project you're working on, take a look at https://hub.docker.com/u/warcforceone and use the images from there
16:04 πŸ”— Terbium thanks
16:53 πŸ”— arkiver pnJay: done
16:58 πŸ”— jc86035 has joined #warrior
17:19 πŸ”— oshura_ has quit IRC (Leaving)
18:00 πŸ”— MrRadar2 has quit IRC (Read error: Operation timed out)
18:18 πŸ”— MrRadar2 has joined #warrior
18:23 πŸ”— MrRadar2 has quit IRC (Read error: Connection reset by peer)
18:30 πŸ”— MrRadar2 has joined #warrior
18:57 πŸ”— oshura has joined #warrior
19:28 πŸ”— DogsRNice has joined #warrior
19:31 πŸ”— britmob has joined #warrior
19:37 πŸ”— atbk has quit IRC (Quit: ZNC - https://znc.in)
19:37 πŸ”— atbk has joined #warrior
19:51 πŸ”— oshura does anyone know what the localhost isp address would be to look at the docker containers on the browser (I asked this earlier but I'm curious if anyone is on now that may know)
19:52 πŸ”— Kaz 127.0.0.1 ?
19:53 πŸ”— oshura I thought so too but it turns out that the containers I have running won't do it with that. As such I went into htop and found out what the ip addresses were via the command names :)
19:53 πŸ”— oshura So actually, never mind lo
19:53 πŸ”— oshura lol
19:55 πŸ”— oshura But thank you Kaz! Now all I have to figure out is how to change where the data is temporarily stored on my pi containers from my SD card to an external. But we're making progress in the right direction
20:14 πŸ”— jc86035 has quit IRC (Quit: Connection closed for inactivity)
20:38 πŸ”— DogsRNice anyone else getting this error a lot? Error communicating with tracker: 502 Server Error: Bad Gateway for url: https://tracker.archiveteam.org:1338/api/done.
20:58 πŸ”— Kaz it's normal
20:58 πŸ”— Kaz I presume it's stopped by now
21:06 πŸ”— phillipsj I was runing out of disk sapce by transfering too much data anyway.
21:31 πŸ”— phillipsj looks like my virtualbox manager froze up. I can force-quit once the VMs finish shutting down.
21:44 πŸ”— Wingy has joined #warrior
21:55 πŸ”— Wingy has quit IRC (Read error: Operation timed out)
21:57 πŸ”— Wingy has joined #warrior
22:02 πŸ”— Wingy4 has joined #warrior
22:03 πŸ”— Wingy has quit IRC (Read error: Operation timed out)
22:03 πŸ”— Wingy4 is now known as Wingy
22:10 πŸ”— Wingy has quit IRC (Read error: Operation timed out)
22:11 πŸ”— Wingy has joined #warrior
22:12 πŸ”— Wingy has quit IRC (Read error: Operation timed out)
22:14 πŸ”— Wingy has joined #warrior
22:21 πŸ”— Wingy5 has joined #warrior
22:21 πŸ”— Wingy has quit IRC (Read error: Operation timed out)
22:21 πŸ”— Wingy5 is now known as Wingy
22:21 πŸ”— VADemon has quit IRC (Read error: Connection reset by peer)
22:21 πŸ”— VADemon has joined #warrior
22:22 πŸ”— Wingy has quit IRC (Client Quit)
22:23 πŸ”— Wingy has joined #warrior
23:15 πŸ”— Wingy What does warrior id do?
23:23 πŸ”— Kaz context?
23:30 πŸ”— oshura-m Hey Wingy I got out to work
23:31 πŸ”— Wingy So you are ready to get the pi working?
23:32 πŸ”— oshura-m I think it is working overall. There’s just some things to fine tune but I’m out at a Christmas party now so no fine tuning for me lol
23:32 πŸ”— oshura-m I still want to see what we can do about some FAQs
23:36 πŸ”— Wingy Maybe a "run this command, come back in 30 minutes, edit this file, docker-compose up"?
23:42 πŸ”— Wingy Kaz: I see `ENV WARRIOR_ID=""` in the warrior dockerfile
23:42 πŸ”— Kaz oh
23:43 πŸ”— Kaz I have absolutely no idea
23:44 πŸ”— Kaz https://github.com/ArchiveTeam/seesaw-kit/blob/699b0d215768c2208b5b48844c9f0f75bd6a1cbc/seesaw/warrior.py#L187
23:44 πŸ”— Kaz Can't see why that'd be useful anywhere though
23:47 πŸ”— Wingy Does it show in the tracker maybe?
23:48 πŸ”— Kaz could do, not sure if I've ever seen it
23:48 πŸ”— Kaz maybe that's because nobody's ever used it, though
23:49 πŸ”— oshura-m That would be good Wingy
23:50 πŸ”— Wingy πŸ‘
23:55 πŸ”— Kaz chfoo: looking at ways to reduce tracker memory usage. Any idea if there's a way to drain old project queues from redis?
23:55 πŸ”— Kaz other than just whacking the destroy queue button

irclogger-viewer