<    March 2017    >
Su Mo Tu We Th Fr Sa  
          1  2  3  4  
 5  6  7  8  9 10 11  
12 13 14 15 16 17 18  
19 20 21 22 23 24 25  
26 27 28 29 30 31
00:09 gbt joined
00:15 cqi joined
00:20 heathsno_ joined
00:25 themurph joined
00:26 jayunit100 joined
00:40 yhchiang joined
00:41 austin987 joined
00:44 techquila joined
00:48 yhchiang joined
00:57 yhchiang joined
00:58 gbt joined
01:02 dumbitguy2 joined
01:08 jimklo_ joined
01:11 yhchiang joined
01:14 bmurt joined
01:32 heathsnow joined
01:32 gully-foyle joined
01:37 techquila joined
01:57 heathsnow joined
02:01 d^sh joined
02:03 dumbitguy2 joined
02:12 techquila joined
02:29 jimklo joined
02:42 jeffreylevesque joined
03:02 cqi joined
03:04 dumbitguy2 joined
03:07 techquila joined
03:41 jane_booty_doe joined
04:04 dumbitguy2 joined
04:05 gableroux joined
04:10 setkeh joined
04:10 setkeh joined
04:15 techquila joined
04:32 TooLmaN joined
05:04 atomekk joined
05:04 atomekk joined
05:05 dumbitguy2 joined
05:07 Deltanic_ joined
05:07 Unknown[- joined
05:07 masterzen joined
05:08 blaisebool joined
05:21 masterzen joined
05:29 jimklo joined
05:36 Repox joined
05:46 Robr3rd joined
05:56 xMopxShell joined
05:59 gableroux joined
05:59 hygl joined
06:06 dumbitguy2 joined
06:13 <Robr3rd> I had to transfer local (machine) user accounts and I when I did this I `rsync`'d over all of my old user's files to my new user. Although largely successful, the downside of this seems to be that Vagrant doesn't know how to cope with this and keeps trying to reference paths to my old User's home folder (MacOS). Any ideas?
06:14 <Robr3rd> I've tried uninstalling/reinstalling Vagrant and VirtualBox, including purging all of the boxes that I had locally, etc.
06:59 gableroux joined
07:07 dumbitguy2 joined
07:10 TomyWork joined
07:16 nshaikh joined
07:27 numbdewd joined
07:27 pLaTo0n joined
07:28 <pLaTo0n> moin
07:39 last_staff joined
07:44 Wanderer- joined
07:49 serque joined
08:08 dumbitguy2 joined
08:18 marcogmonteiro joined
08:18 Robr3rd left
08:23 nshaikh joined
08:27 jane_booty_doe joined
08:30 gableroux joined
08:43 notebox joined
08:47 pigeons joined
08:48 gbt joined
09:05 bmurt joined
09:08 dumbitguy2 joined
09:11 electrofelix joined
09:13 gbt joined
09:18 kjsaihs joined
09:33 caitlinb_ joined
09:42 mortenie joined
09:49 csotelo joined
09:50 jwd joined
10:00 gbt joined
10:01 gbt_ joined
10:09 dumbitguy2 joined
10:31 jeeva_ joined
10:34 PHPanos joined
11:00 gableroux joined
11:10 dumbitguy2 joined
11:30 <jeeva_> how to change the VM name in vagrant
11:36 <fengor> config.vm.define "wildfly" do |wildfly|
11:36 <fengor> wildfly.vm.hostname = "wildfly"
11:40 <jeeva_> thanks
11:40 infernix joined
11:41 PHPanos joined
11:41 <fengor> no prob
11:41 jayunit100 joined
11:48 bmurt joined
11:55 pLaTo0n joined
12:03 wlightning-fuel joined
12:07 gableroux joined
12:10 dumbitguy2 joined
12:16 PHPanos joined
12:17 antgel joined
12:19 kpease joined
12:21 gableroux joined
12:22 swills joined
12:22 gableroux joined
12:26 gablerou_ joined
12:27 snowmizer joined
12:28 ira joined
12:33 gableroux joined
12:49 PHPanos joined
12:59 jeffreylevesque joined
13:04 nunchuck joined
13:05 anonymouse joined
13:05 <nunchuck> trying to install vagrant 1.9 on ubuntu 16.10 and getting these errors https://pastebin.com/RfhhREiC
13:08 r_x joined
13:11 dumbitguy2 joined
13:13 PHPanos joined
13:16 wlightning-fuel joined
13:18 BenG joined
13:19 BenG left
13:19 KurTT joined
13:20 snowmizer joined
13:20 budhram joined
13:22 <KurTT> Hey guys, I've been all over google around this issue and probably read all the posts about it but still can't pin down the problem.. I'm running vagrant + ansible, and synced_folder with NFS. NFS is set up just fine. The problem I have is when I'm trying to change permissions on files from the guest VM. "chown: changing ownership of ...: Operation not permitted". I'm on ubuntu 16.04, running vagrant 1.8.5 and virtualbox 5.1.18. Could you point me in the
13:22 <KurTT> right direction perhaps?
13:25 BenG joined
13:35 wlightning-fuel joined
13:37 mortenie joined
13:38 dumbitguy2 joined
13:42 computeracer joined
14:03 wandering_vagran joined
14:23 PHPanos joined
14:24 tapoxi joined
14:35 PHPanos joined
14:43 choke joined
14:46 jayunit100 joined
14:59 cornfeedhobo joined
14:59 dbclk joined
15:04 pgdagenais joined
15:15 wandering_vagran joined
15:17 infernix joined
15:27 wandering_vagran left
15:52 holodoc joined
15:52 TomyWork joined
16:01 holodoc joined
16:09 notebox joined
16:10 SesMan joined
16:21 bmurt joined
16:23 heathsnow joined
16:30 marcogmonteiro joined
17:12 atomekk joined
17:16 multi_io joined
17:16 GenteelBen joined
17:20 holodoc joined
17:43 KurTT joined
17:46 Bnaya joined
18:00 bekks joined
18:00 bekks joined
18:17 holodoc joined
18:21 raynold joined
18:23 jwd joined
18:29 apetresc joined
18:37 serque joined
18:43 austin987 joined
18:46 hygl joined
18:49 notebox joined
18:53 preyalone joined
18:55 tapoxi joined
19:01 todd_dsm joined
19:08 themurph joined
19:18 Bass10 joined
19:22 jimklo joined
19:25 mihok joined
19:27 GOLDPANK joined
19:31 bmurt joined
19:53 uniq joined
19:56 Bnaya joined
20:11 serque joined
20:23 bmurt joined
20:26 Bnaya joined
20:29 vexoon joined
20:30 jeffreylevesque joined
21:22 holodoc joined
21:39 systest joined
21:45 <systest> just upgraded from v1:1.9x to 1:1.9.3 and now I'm getting a console.log file on each `vagrant up` . Haven't set VAGRANT_LOG env var. Is there something I can add to Vagrantfile to disable this behavior? (couldn't find t in the docs)
21:53 atomi joined
21:53 Helio- joined
21:53 <Wanderer-> systest, https://www.vagrantup.com/docs/other/environmental-variables.html#vagrant_log
21:54 <systest> Wanderer-, thanks. However, per above, I haven't set that i.e. default should be no log
21:54 <systest> or have I missed something?
21:56 rancyd joined
21:56 <Wanderer-> I am not quite sure, whats in the console.log file exactly?
21:57 <Wanderer-> Or the whole log of the `vagrant up` output is there?
21:59 <Wanderer-> systest, try redirecting the output to /dev/null maybe and see if that works? Like mentioned here https://www.vagrantup.com/docs/other/debugging.html
22:03 <systest> It's not on stdout, it's an actual file which is being created, i.e. `ubuntu-xenial-16.04-cloudimg-console.log` Maybe it's virtualbox or the ubuntu xenial image?
22:03 <systest> i'll dig a bit more
22:03 <systest> thanks for the suggestions, appreciate the reply
22:07 <systest> Wanderer-, sorry, multitasking badly
22:07 <systest> content of log is the guest console, e.g the stuff you'd see with dmesg or at boot on the VTTY
22:08 <systest> starting to think ubuntu has done something in their box image
22:09 <Wanderer-> systest, then maybe just write a small shell script which deletes the log file
22:10 <systest> y, plenty of ways I could remove it. just curious as to why something is suddenly writting files into the host's FS
22:10 <Wanderer-> My guess is, it writes if an error happened.
22:10 <systest> possible
22:11 atomi joined
22:11 <systest> have to run and it's low priority, will revist tomorrow. thanks for the thoughts
22:11 <Wanderer-> Good luck.
22:12 <systest> tks
22:14 atomi joined
22:16 holodoc joined
22:26 holodoc joined
22:34 techquila joined
22:40 ExtraSteve left
23:06 uniq joined
23:29 stanchan joined
23:41 jayunit100 joined
23:45 holodoc joined
23:45 austin987 joined