by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Rajendra kadam
    @raju249_gitlab
    I think @leetickett_gitlab has some experience with it
    Lee Tickett
    @leetickett_gitlab
    haha- yes I used to use it until a few days ago moving from windows to Ubuntu
    what o/s do you have on your host machine?
    Łukasz Groszkowski
    @falxcerebri_gitlab
    Ubuntu 20.04
    I'm getting this:
    Go version 1.13.4 detected, please install Go version 1.14 or higher.
    Makefile:131: recipe for target 'preflight-checks' failed
    make: *** [preflight-checks] Error 1
    Lee Tickett
    @leetickett_gitlab
    ah yes I should definitely be able to help with that
    Łukasz Groszkowski
    @falxcerebri_gitlab
    well, it's nothing serious, I guess Vagrantfile is missing some config
    Lee Tickett
    @leetickett_gitlab
    kind of- for some reason the Go version was changed in the Vagrantfile but then rolled back
    Łukasz Groszkowski
    @falxcerebri_gitlab

    oh and another thing :

          cpus = Facter.value('processors')['count']
          if facter_mem = Facter.value('memory')
            mem = facter_mem.slice! " GiB".to_i * 1024
          elsif facter_mem = Facter.value('memorysize_mb')
            mem = facter_mem.to_i
          else
            raise "unable to determine total host RAM size"
          end
    
          # disables NFS on macOS to prevent UID / GID issues with mounted shares
          enable_nfs = !Vagrant::Util::Platform.platform.match?(/darwin/)
          enable_shares(override, enable_nfs)

    this doesn't work on Ubuntu 20.04 either

    Lee Tickett
    @leetickett_gitlab
    i think maybe because 1.14 is only available in certain versions of Ubuntu
    Łukasz Groszkowski
    @falxcerebri_gitlab
    But that's inside VM, so one should be able to pick the right version, right?
    I had to short-circuit it to something really dumb like:
          mem = 6144
          cpus = 8
    
          # disables NFS on macOS to prevent UID / GID issues with mounted shares
          enable_nfs = !Vagrant::Util::Platform.platform.match?(/darwin/)
          enable_shares(override, enable_nfs)
    Before I familiarized myself with Vagrant, I've used KVM with Ubuntu 18.04 and it worked like a charm, just following the Readme from GDK
    Lee Tickett
    @leetickett_gitlab
    if you're using Ubuntu on your host system I would probably just run it natively
    what was your thinking behind using vagrant? just quicker to get up and running?
    sudo add-apt-repository ppa:longsleep/golang-backports
    export GDK_GO_VERSION="1.14" export PATH="/usr/lib/go-${GDK_GO_VERSION}/bin:$PATH"
    should be a carriage return/new line between those two export commands
    sudo apt-get install golang-${GDK_GO_VERSION}-go
    Łukasz Groszkowski
    @falxcerebri_gitlab

    Okay so, at the time I've attempted to install GDK on my host, I failed as not all packages were available for 20.04. So I figured out, why not make a VM with Ubuntu 18? I wasn't familiar with Vagrant at that time so I've picked KVM. I've installed everything manually inside VM and it did the trick.

    Recently however, I've faced other issues with other projects and had my colleagues recommended to use Vagrant for thinner VMs. I found that really nice as Vagrant file has everything configured, I'm just running vagrant up and in few minutes I have VM ready to do some particular job. Plus I can share Vagrantfile with friends.

    So I was expecting the same thing from Vagrant file in GDK - I'll run vagrant up and everything will setup inside.

    Lee Tickett
    @leetickett_gitlab
    that's how it should work in theory- unfortunately i've rarely found that
    Łukasz Groszkowski
    @falxcerebri_gitlab
    It's not a problem I can't setup VM/Vagrantfile, rather that Vagrantfile is somewhat brittle. (I have Vagrant and VirtualBox up to date)
    Okay. Perhaps I could help with improving Vagrantfile for Ubuntu hosts
    I'm sure that this would lower the entry effort
    Łukasz Groszkowski
    @falxcerebri_gitlab
    @leetickett_gitlab should I file an issue for that and try to help improve Vagrantfile for Ubuntu?
    Lee Tickett
    @leetickett_gitlab
    i think that would be very helpful although i've obviously got frustrated and lost hope a little hence why i've moved to unbuntu host
    I can share my exact steps for getting it working on ubuntu 20 native if that's helpful?
    i think it makes life a lot easier and improved performance amongst other things running native
    Łukasz Groszkowski
    @falxcerebri_gitlab
    Well, honestly if I'm going into Vagrant I'd use Ubuntu 18 as I had no issue what so ever with it on KVM. Just following the readme
    Ubuntu 20.04 is still fresh and I'm not sure that all packages are already available
    Lee Tickett
    @leetickett_gitlab
    to be fair, i mostly followed the readme with Ubuntu 20
    i have it all working- dont think i hit any real issues
    Łukasz Groszkowski
    @falxcerebri_gitlab
    Yeah, maybe the packages I've missed were published recently
    I've tried it like 2-3 weeks after Ubuntu 20.04 came out
    So if you had no issues and didn't have to compile manually or override repositories, I can give it a go on Ubuntu 20.04, but I still think that using 18.04 is sufficient.
    Lee Tickett
    @leetickett_gitlab
    yes- give 20 a go- think you'll be fine :)
    Łukasz Groszkowski
    @falxcerebri_gitlab
    I'm no expert with Vagrant thou, and one question, considering people are still using 18.04 is it fine to have guest OS > host OS?
    Lee Tickett
    @leetickett_gitlab
    yes- in theory the host os shouldn't really have any impact
    although i found with windows as host os the shares aren't compatible
    Łukasz Groszkowski
    @falxcerebri_gitlab
    okay, that's set then.
    Should I file an issue in GDK or elsewhere?
    Lee Tickett
    @leetickett_gitlab
    definitely on GDK
    i would be surprised if there isn't already one
    Łukasz Groszkowski
    @falxcerebri_gitlab
    I'll take a look first
    Lee Tickett
    @leetickett_gitlab
    but maybe like me others have been lazy and just fixed the issue and not filed it :)
    you may be interested in my longwinded issue with all the problems i have/had in vagrant: gitlab-org/gitlab-development-kit#868
    Paul Slaughter
    @pslaughter_gitlab
    Just double checking... This is a good place to reference a community contributor to ask for help if running into GDK issues?
    Lee Tickett
    @leetickett_gitlab
    @pslaughter_gitlab absolutely :thumbsup:
    Ray Paik
    @rpaik_gitlab
    @pslaughter_gitlab yes, I think a lot of community members found it helpful as experienced contributors (like @leetickett_gitlab, @raju249_gitlab and others) have been generous offering help/suggestions on GDK...
    Paul Slaughter
    @pslaughter_gitlab
    Thanks @leetickett_gitlab & @rpaik_gitlab! :bow: