<    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:11 winem_ joined
00:11 enderandpeter joined
00:24 kerosene_ joined
00:28 mihok joined
00:39 sum1 left
00:39 livingstn joined
00:42 techquila joined
00:44 phyber joined
00:49 techquila joined
00:52 livingstn joined
01:01 themurph joined
01:10 xtal joined
01:16 stanchan joined
01:16 pawnbox joined
01:30 jayunit100 joined
01:44 PaulCapestany joined
01:46 pawnbox joined
01:51 tofutoon joined
01:53 <tofutoon> Is there an easy way to set the root password using a Vagrantfile? I can do it manually with sudo passwd root, but I'd like to do this with a Vagrant shell script.
02:02 mihok joined
02:30 d^sh joined
02:32 techquila joined
02:39 bmurt joined
02:39 jimklo_ joined
03:01 manjaro-kde5-- joined
03:04 cqi joined
03:09 <shadoxx> tofutoon: really easy. just put the passwd command into a script and pipe the new password into it
03:12 xtal joined
03:25 pawnbox joined
03:31 zerocool_ joined
03:32 bmurt joined
03:32 frank1 joined
03:33 brendan- joined
03:54 techquila joined
03:55 pawnbox joined
04:09 <tofutoon> shadoxx: Thanks. That helps.
04:19 dbclk joined
04:24 zerocool_ joined
04:29 _3dwardsharp joined
04:42 <dbclk> anyone around?
04:42 pawnbox joined
04:44 budhram joined
04:51 ksclarke joined
05:08 techquila joined
05:13 xtal joined
05:14 pawnbox_ joined
05:22 zerocool_ joined
05:38 atomekk joined
06:05 pawnbox joined
06:06 Olympionex joined
06:08 <Olympionex> I'm having issues with synced folders using vagrant 1.8.1 and 1.9.2 on Ubuntu 16.04. I am using a docker provider. Using the basic folder sync, I cannot find a way to allow a non root user to write to the synced_folder in the container. I h
06:09 <Olympionex> I have tried the mount options, but they did not seem to change anything
06:10 <Olympionex> I then tried using an NFS synced folder, but I get the "No host IP was given to the Vagrant core NFS helper..." message which seems to have an open ticket item since Nov 2016
06:11 <Olympionex> is there no presently not way to allow a non root user to write to the synced directory?
06:16 pawnbox joined
06:38 Repox joined
06:39 <shadoxx> Olympionex: you can change the owner of the synced folder in the vagrant config i believe
06:39 <shadoxx> http://stackoverflow.com/questions/13169154/cannot-change-permissions-of-folders-within-vagrant-home-folder
06:40 <shadoxx> looks like you can add :owner=> 'vagrant'
06:42 <Olympionex> shadoxx: hmm, i originally tried that and then spent a lot of time trying to get the dmode and fmode to work. Maybe I was doing something wrong. Are the owner and group supposed to correspond to ones in the container or on the host?
06:43 <shadoxx> Olympionex: generally the one in the container. the regular user is 'vagrant'. you want the owner and group to be 'vagrant'. Ignore the dmode and fmode, as I don't think they're needed
06:43 <shadoxx> ie, the defaults are good enough once the ownership is set
06:43 <shadoxx> I know it works. I have quite a few Ubuntu images that use the Ubuntu 14.04 and 16.04 image. It's possible something has changed and you're encountering a bug I haven't seen, but I'd have to test on my local machine to check
06:46 <shadoxx> Olympionex: you could also be hitting a condition where your host OS is disallowing writing to the directory your Vagrantfile is in too. i've seen that on Windows in earlier versions of Vagrant. i don't dev on Windows anymore so i can't test that
06:47 <Olympionex> oh, well there is a problem with the permissions though because they are still 755
06:47 <Olympionex> hang on
06:49 <Olympionex> well, now I have the directory with uid 1001 and group sudo
06:49 <Olympionex> but the UID of my user is 1000
06:51 <Olympionex> there is no 1001 in /etc/passwd, but 1001 is the uid of the user i'm running as on host ( which is not the user I have set as group / owner in the vagrant file)
06:51 <shadoxx> what host OS, out of curiosity?
06:51 <Olympionex> ubuntu 16.04
06:52 <shadoxx> are you working out of your home directory?
06:52 <shadoxx> ie, a Projects folder in ~
06:52 <Olympionex> yeah
06:52 <shadoxx> are permissions on that directory proper?
06:52 <shadoxx> On the host
06:53 last_staff joined
06:54 bbradley joined
06:54 <Olympionex> hmm, the group ownership is odd I think, sudo for some reason
06:55 <Olympionex> thats for the whole /home/user
06:55 <Olympionex> although my project dir seems fine, user and group is me
06:55 bbradley joined
06:59 <Olympionex> ok, well now that i fixed that, both the user and group is now 1001 for the synced folder
07:00 <Olympionex> i wonder where its getting the 1001 from instead of the 1000
07:00 <shadoxx> can you do 'id' in the vagrant image and check?
07:00 <shadoxx> yeah, having 'sudo' as the group owner is kind of weird
07:01 <shadoxx> on a 16.04 host, it should always be <username>:<username>
07:01 <shadoxx> unless you have some weird admin structure or someone has changed it for reasons
07:01 <Olympionex> no, I assume it was a bad command on my part
07:02 sub-mod joined
07:02 <Olympionex> yeah, inside the vagrant container, all I see is a UID of 1000 for my user (dev)
07:02 <Olympionex> uid=1000(dev) gid=1000(dev) groups=1000(dev),27(sudo)
07:06 sparr left
07:07 <Olympionex> was also interesting, my username was not a member of my user group, only sudo -- maybe when i created the user I set the primary group to sudo somehow
07:07 pawnbox joined
07:08 <Olympionex> i just changed the user / group in the Vagrantfile to 'vagrant' just to see what it would do, and its still 1001
07:08 JohnDoe2 joined
07:08 bbradley joined
07:09 <Olympionex> config.vm.synced_folder "./src", "/home/dev/BulkTransferNav", owner: 'vagrant', group: 'vagrant'
07:09 <Olympionex> before was: config.vm.synced_folder "./src", "/home/dev/BulkTransferNav", owner: 'dev', group: 'dev'
07:09 <Olympionex> doesn't seem to change anything there
07:11 <Olympionex> tried with root as well, no change. Seems to just be getting it directly from the host
07:11 techquila joined
07:13 bbradley joined
07:14 xtal joined
07:16 <Olympionex> alright, thanks for the help shadoxx -- i've got to leave but may be back later
07:16 <shadoxx> sorry, just saw your reply
07:16 <shadoxx> i'll be on tomorrow definitely
07:17 <shadoxx> sounds like you may have some user problems on your host you should work out. improper user creation would definitely cause weird issues like what you're seeing
07:26 voxxit joined
07:27 _3dwardsharp joined
07:35 manjaro-kde5-- joined
07:37 bbradley joined
07:45 ekem joined
07:49 tofutoon left
07:59 rickardve joined
08:05 GenteelBen joined
08:07 bbradley joined
08:16 TomyWork joined
08:19 PHPanos joined
08:34 antgel joined
08:39 mortenie joined
08:50 pawnbox joined
09:00 _ADN_ joined
09:01 wandering_vagran joined
09:05 serque joined
09:10 marcogmonteiro joined
09:15 xtal joined
09:17 pawnbox joined
09:18 _ADN_ joined
09:31 jwd joined
09:35 TheBrayn joined
09:36 themurph joined
09:48 freezer joined
09:52 cqi joined
09:52 electrofelix joined
09:53 es3l3k joined
09:55 pawnbox joined
09:57 es3l3k joined
10:03 RxMcDonald joined
10:04 <RxMcDonald> Hello, anyone knows how to access the machine that is being hosted on my wifi hotspot from my host machine?
10:04 <RxMcDonald> Trying the ip address shown on the machine but it gets stuck loading, i.e. not responding
10:05 <RxMcDonald> timed out
10:05 <RxMcDonald> It works if I bridge to ethernet tho
10:06 pawnbox joined
10:08 abacao joined
10:09 <RxMcDonald> I can't find the 192.168.2.3 of my vagrant machine that is bridged to wifi from my host machine that is sharing wifi with hotspot
10:10 mfournier joined
10:12 pawnbox joined
10:13 <RxMcDonald> anyone ? :'(
10:15 <RxMcDonald> probably not possible
10:21 <es3l3k> RxMcDonald: Define what you mean by access?
10:26 moozer joined
10:26 _ADN_ joined
10:30 versedi joined
10:37 moozer joined
10:43 _ADN_ joined
10:58 <RxMcDonald> es3l3k: ping or w/e, can't find it from my host browser
11:04 atomekk joined
11:04 atomekk joined
11:14 pawnbox joined
11:16 xtal joined
11:17 freezer joined
11:19 <aredpanda`w> Does Vagrant provide a way of booting up machines without bein in their respective folder? I wanna bring up my machines from anywhere in my system, I tried using the machine ids but to no avail.
11:23 jayunit100 joined
11:24 <ccooke> aredpanda`w: You can write a script that changes to the directory and then starts the VM
11:25 pawnbox joined
11:41 serque joined
11:43 serque1 joined
11:44 saintromuald joined
11:51 Natrick joined
11:59 PHPanos joined
12:06 pawnbox joined
12:06 bbradley joined
12:08 moozer joined
12:09 mihok joined
12:12 abacao joined
12:14 abacao_ joined
12:20 _ADN_ joined
12:28 caitlinb joined
12:32 <es3l3k> RxMcDonald: have you tried 'vagrant ssh'?
12:32 <es3l3k> aredpanda`w: what operating system do you use?
12:38 mortenie joined
12:39 habitullence joined
12:39 mutin-s joined
12:42 notebox joined
12:46 kpease joined
12:48 kpease_ joined
12:51 joevano joined
12:52 _ADN_ joined
12:55 Ced-le-pingouin joined
12:55 pawnbox joined
12:57 marcogmonteiro joined
12:58 dbclk joined
12:59 backjlack joined
13:00 gableroux joined
13:05 computeracer joined
13:12 atomekk joined
13:15 pawnbox joined
13:16 xtal joined
13:17 snowmizer joined
13:17 pawnbox_ joined
13:21 pawnbox joined
13:30 GenteelBen joined
13:32 GenteelBen joined
13:34 GenteelBen joined
13:35 mihok joined
13:40 aboudreault joined
13:41 marcogmonteiro joined
13:48 pawnbox joined
13:50 ira joined
13:57 pgdagenais joined
13:57 mortenie joined
13:57 backjlack joined
13:58 jeffreylevesque joined
13:59 aboudreault joined
13:59 aboudreault joined
14:01 antgel joined
14:03 jeffreylevesque_ joined
14:04 pawnbox joined
14:08 aboudreault joined
14:09 bmurt joined
14:13 livingstn joined
14:14 jeffreylevesque joined
14:18 pgdagenais joined
14:24 jeffreylevesque_ joined
14:31 aboudreault joined
14:31 Pradeep_ joined
14:33 xtal joined
14:34 jeffreylevesque joined
14:38 ahrs joined
14:40 notebox joined
14:44 jeffreylevesque_ joined
14:53 techquila joined
14:54 jeffreylevesque joined
14:56 caitlinb_ joined
14:56 moozer joined
14:58 Takumo joined
14:58 Takumo joined
15:00 ujjain joined
15:00 ujjain joined
15:04 jeffreylevesque_ joined
15:06 tapoxi joined
15:14 jeffreylevesque joined
15:16 pawnbox joined
15:24 snowmizer2 joined
15:24 jeffreylevesque_ joined
15:29 fcoelho joined
15:29 fcoelho joined
15:34 jeffreylevesque joined
15:42 jeffreylevesque_ joined
15:43 <digi691> If using linux VAGRANT_CWD=[The directory of your vagrant file] vagrant cmd
15:44 pseydtonne joined
15:51 jeffreylevesque joined
15:56 budhram joined
15:57 jeffreylevesque_ joined
16:03 wlightning-fuel joined
16:07 jeffreylevesque joined
16:11 abacao joined
16:17 jeffreylevesque_ joined
16:18 pgdagenais joined
16:20 RxMcDonald left
16:21 TheBrayn left
16:22 zerocool_ joined
16:22 mfournier joined
16:26 pseydtonne joined
16:27 jeffreylevesque joined
16:29 bmurt joined
16:31 sub-mod joined
16:31 pLaTo0n joined
16:32 enderandpeter joined
16:33 raynold joined
16:33 caitlinb joined
16:34 platoon__ joined
16:35 bmurt joined
16:38 jeffreylevesque_ joined
16:39 mihok joined
16:41 wandering_vagran left
16:46 dwi left
16:48 jeffreylevesque joined
16:50 mortenie joined
16:54 PHPanos joined
17:09 wlightning-fuel joined
17:10 wlightning-fuel joined
17:13 multi_io joined
17:19 Edgan joined
17:21 abacao joined
17:22 pawnbox joined
17:33 pseydtonne joined
17:41 enderandpeter joined
17:42 pgdagenais joined
17:44 pawnbox joined
17:57 ahrs joined
18:12 jimklo joined
18:12 pawnbox joined
18:13 jimklo joined
18:20 techquila joined
18:20 v0rtex joined
18:26 Wanderer- joined
18:27 last_staff1 joined
18:30 jeffreylevesque joined
18:33 vhosakot joined
18:35 <vhosakot> hi, I see each vagrant VM use more than 200% CPU on my vagrant host and I cannot SSH into some of the vagrant VMs. My vagrant host has 16 CPUs and 32G RAM, and I'm using libvirt vagrant driver. Can anyone help me debug? - http://paste.openstack.org/show/602108/
18:37 <vhosakot> can I open an enhancement bug to propose a "vagrant top" command (similar to "docker top" command) to display the CPU and memory stats of the processes running in a vagrant VM on the vagrant host. "vagrant top" will be helpful to debug the issue I'm seeing where each vagrant uses more than 200% CPU on the vagrant host, and I cannot SSH into the vagrant VM. Let me know!? :)
18:40 <spox> if vagrant is unable to ssh into the vms it is managing then it will not be able to get a current process list from the guest vm as it is unable to connect
18:43 <vhosakot> spox: right, that is a great point, isn't "vagrant top" a nice command to check stats of the vm when we _can_ SSH into the vagrant vm? but, yeah, I can't even SSH in my case since each vm is using more than 200% CPU on the vagrant host :(
18:44 realitygaps joined
18:46 <vhosakot> spox: any idea why the vagrant guest VM is using 200% CPU on the vagrnat host?
18:46 <vhosakot> vagrant*
18:47 stormmore joined
18:48 enderandpeter joined
18:54 jeffreylevesque_ joined
19:03 <Wanderer-> vhosakot, doesnt libvirt provide a log file?
19:06 giarc joined
19:07 <vhosakot> Wanderer-: it does. I see these errors in the libvirt logs - http://paste.openstack.org/show/602113/
19:08 nickel_dime_look joined
19:09 nickel_dime_look left
19:12 dbclk joined
19:17 stormmore joined
19:17 Repox joined
19:18 <vhosakot> lol, nobody likes the "vagrant top" proposal?:)
19:19 andrzejku joined
19:26 kpease joined
19:30 OnceMe joined
19:31 <OnceMe> is there official vagrant box for debian 8? or I need to build a base box?
19:36 brianjsw_ joined
19:37 <brianjsw_> not sure if this is due to the new VirtualBox maintenance release or not... but exact same box that was working yesterday, today gives message it cannot mount vagrant shared folder and vagrant up aborts
19:37 <brianjsw_> Error: no such file or directory on: mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant
19:39 <OnceMe> brianjsw_: what box?
19:39 <OnceMe> from where have you dl the box, or you made a base box?
19:39 <brianjsw_> ubuntu/xenial64
19:40 <OnceMe> dl from where?
19:40 <brianjsw_> I believe vagrantcloud.com
19:41 sub-mod joined
19:41 <brianjsw_> just did a Vagrantfile
19:41 <brianjsw_> and it says:
19:41 <computeracer> Hello, Has anyone seen the transport: ssh_key field being ignored in .kitchen.yml and ec2 driver?
19:41 <brianjsw_> config.vm.box = "ubuntu/xenial64"
19:43 OnceMe joined
19:48 <spox> vhosakot: it's a fine proposal. might be best as a plugin if you want to implement it :)
19:54 <vhosakot> spox: wow, I dont have time time to implement it, I'll open the bug, and might help implement if any developers are ready to help :) it would be helpful instead of ssh'ing inside and checking top in each VM :)
19:58 wlightning-fuel joined
20:00 xmj joined
20:00 <xmj> moin
20:01 <xmj> is there a way I can provision a particular ssh pubkey to some user, in addition to the one provided by Ansible?
20:03 spaok_ joined
20:03 <spaok_> hi all
20:05 <spaok> does anyone know how to prevent vagrant from adding the vagrant user and use the ubuntu user I put in the image with packer?
20:05 <spox> spaok: do you mean using your custom user for the ssh communicator?
20:06 <spaok> ya, but after I put the box in vagrant and up it, the ubuntu user is gone and the vagrant user is added
20:06 <spaok> I tried using config.ssh.username
20:07 <spox> are you sure the ubuntu user is gone?
20:07 <spaok> but since the user seems to be getting removed
20:07 <spaok> we'll I ran the same packer process, kept the input files, converted it to vdi and loaded it in virtualbox and the user was there
20:08 <spaok> so either the packer vagrant post-process is doing something or vagrant up is
20:08 <spox> then i would confirm you have properly loaded the box into vagrant. sounds like it's either using the wrong box name, or you haven't added it properly.
20:08 <spox> vagrant won't remove a user from a newly started guest
20:08 <spox> unless you have a provision script enabled to do that
20:08 <spaok> I don't but I'm using libvirt so maybe its doing something
20:09 <spaok> shouldn't be
20:10 stormmore joined
20:11 brianjsw_ joined
20:12 vhosakot_ joined
20:12 floreo joined
20:13 pawnbox joined
20:14 PHPanos joined
20:15 <brianjsw_> Yep it's the new version of VirtualBox
20:15 <brianjsw_> Downgraded to 5.1.14 and the problem went away
20:18 enderandpeter joined
20:23 <OnceMe> I have an issue with shared foldwers
20:23 <OnceMe> Vagrant was unable to mount VirtualBox shared folders. This is usually
20:24 <OnceMe> Ihave this: config.vm.synced_folder "/var/www/bleh", "/vagdata"
20:24 <OnceMe> this /var/www/bleh is on my pc and I wish to access it on vagrant at /vagdata
20:24 <OnceMe> Ive installed sudo apt-get install virtualbox-guest-additions-iso
20:24 <OnceMe> but still this error happens
20:39 pawnbox joined
20:44 stormmore joined
20:47 techquila joined
20:56 frankkahle left
21:08 _ADN_ joined
21:08 enderandpeter joined
21:11 brianjsw joined
21:15 jimklo joined
21:16 andrzejku joined
21:17 Limix joined
21:17 ira joined
21:27 ujjain joined
21:27 ujjain joined
21:38 OnceMe joined
21:38 <OnceMe> is there any problem with debian boxes? I cannot to configure private network ip from some reason
21:39 <OnceMe> this works on ubuntu precise and rest of boxes..
22:00 kerosene joined
22:04 jeffreylevesque joined
22:18 pawnbox joined
22:24 enderandpeter joined
22:28 bmurt joined
22:29 gableroux joined
22:51 jimklo joined
22:55 jimklo joined
22:58 pawnbox joined
22:59 enderandpeter joined
23:09 jeffreylevesque joined
23:16 jimklo_ joined
23:25 mihok joined
23:27 Olympionex joined
23:28 pawnbox joined
23:46 Repox joined
23:51 xMopxShell joined
23:59 Wanderer- joined