[vpsFree.cz: community-list] Gitlab CI s Docker

Petr Parolek petr.parolek at gmail.com
Fri May 12 22:00:15 CEST 2017 

Tak vše nějak zvláštně začalo dobře fungovat - snad je vše vyřešeno.

Díky moc všem


Petr

2017-05-12 15:54 GMT+02:00 Petr Parolek <petr.parolek at gmail.com>:

> Po restartu vps řve zas něco jiného:
>
> /root/.vagrant.d/gems/2.2.5/gems/fog-libvirt-0.3.0/lib/
> fog/libvirt/requests/compute/dhcp_leases.rb:8:in `dhcp_leases': Call to
> virNetworkGetDHCPLeases failed: internal error: no lease with matching MAC
> address: 52:54:00:c3:92:75 (Libvirt::Error)
>
>
> 2017-05-12 15:41 GMT+02:00 Petr Parolek <petr.parolek at gmail.com>:
>
>> Už jo, dal jsem touch /etc/export.
>>
>> Doinstaloval jsem přes sudo apt-get install nfs-kernel-server
>>
>> Zase to řve:
>>
>> ==> default: Mounting NFS shared folders...
>> The following SSH command responded with a non-zero exit status.
>> Vagrant assumes that this means the command failed!
>>
>> mount -o vers=4 192.168.121.1:/root/vagrant /vagrant
>>
>> Stdout from the command:
>>
>>
>>
>> Stderr from the command:
>>
>> mount.nfs: Protocol not supported
>>
>>
>> Dne 12. května 2017 15:35 Matěj Koudelka <matej at hxpro.cz> napsal(a):
>>
>> teda netuším k čemu to potřebuje nfs, ale máš tam ten /etc/exports ?
>>>
>>> Dne 12. května 2017 15:21 Petr Parolek <petr.parolek at gmail.com>
>>> napsal(a):
>>>
>>> Ehmm, měl jsem vyplé kvm v vpsadmin. Ale zas jiná chyba:
>>>> "/opt/vagrant/embedded/gems/gems/vagrant-1.9.4/plugins/hosts/linux/cap/nfs.rb:114:in
>>>> `stat': No such file or directory @ rb_file_s_stat - /etc/exports
>>>> (Errno::ENOENT)" NFS mám zaplé v vpsadminu.
>>>>
>>>> Dne 12. května 2017 14:47 Petr Parolek <petr.parolek at gmail.com>
>>>> napsal(a):
>>>>
>>>> Už to zkoumám.
>>>>>
>>>>> cat Vagrantfile
>>>>> # -*- mode: ruby -*-
>>>>> # vi: set ft=ruby :
>>>>>
>>>>> # All Vagrant configuration is done below. The "2" in Vagrant.configure
>>>>> # configures the configuration version (we support older styles for
>>>>> # backwards compatibility). Please don't change it unless you know what
>>>>> # you're doing.
>>>>> Vagrant.configure("2") do |config|
>>>>>   # The most common configuration options are documented and commented
>>>>> below.
>>>>>   # For a complete reference, please see the online documentation at
>>>>>   # https://docs.vagrantup.com.
>>>>>
>>>>>   # Every Vagrant development environment requires a box. You can
>>>>> search for
>>>>>   # boxes at https://atlas.hashicorp.com/search.
>>>>>   config.vm.box = "debian/jessie64"
>>>>>
>>>>>   # Disable automatic box update checking. If you disable this, then
>>>>>   # boxes will only be checked for updates when the user runs
>>>>>   # `vagrant box outdated`. This is not recommended.
>>>>>   # config.vm.box_check_update = false
>>>>>
>>>>>   # Create a forwarded port mapping which allows access to a specific
>>>>> port
>>>>>   # within the machine from a port on the host machine. In the example
>>>>> below,
>>>>>   # accessing "localhost:8080" will access port 80 on the guest
>>>>> machine.
>>>>>   # NOTE: This will enable public access to the opened port
>>>>>   # config.vm.network "forwarded_port", guest: 80, host: 8080
>>>>>
>>>>>   # Create a forwarded port mapping which allows access to a specific
>>>>> port
>>>>>   # within the machine from a port on the host machine and only allow
>>>>> access
>>>>>   # via 127.0.0.1 to disable public access
>>>>>   # config.vm.network "forwarded_port", guest: 80, host: 8080,
>>>>> host_ip: "127.0.0.1"
>>>>>
>>>>>   # Create a private network, which allows host-only access to the
>>>>> machine
>>>>>   # using a specific IP.
>>>>>   # config.vm.network "private_network", ip: "192.168.33.10"
>>>>>
>>>>>   # Create a public network, which generally matched to bridged
>>>>> network.
>>>>>   # Bridged networks make the machine appear as another physical
>>>>> device on
>>>>>   # your network.
>>>>>   # config.vm.network "public_network"
>>>>>
>>>>>   # Share an additional folder to the guest VM. The first argument is
>>>>>   # the path on the host to the actual folder. The second argument is
>>>>>   # the path on the guest to mount the folder. And the optional third
>>>>>   # argument is a set of non-required options.
>>>>>   # config.vm.synced_folder "../data", "/vagrant_data"
>>>>>
>>>>>   # Provider-specific configuration so you can fine-tune various
>>>>>   # backing providers for Vagrant. These expose provider-specific
>>>>> options.
>>>>>   # Example for VirtualBox:
>>>>>   #
>>>>>   # config.vm.provider "virtualbox" do |vb|
>>>>>   #   # Display the VirtualBox GUI when booting the machine
>>>>>   #   vb.gui = true
>>>>>   #
>>>>>   #   # Customize the amount of memory on the VM:
>>>>>   #   vb.memory = "1024"
>>>>>   # end
>>>>>   #
>>>>>   # View the documentation for the provider you are using for more
>>>>>   # information on available options.
>>>>>
>>>>>   # Define a Vagrant Push strategy for pushing to Atlas. Other push
>>>>> strategies
>>>>>   # such as FTP and Heroku are also available. See the documentation at
>>>>>   # https://docs.vagrantup.com/v2/push/atlas.html for more
>>>>> information.
>>>>>   # config.push.define "atlas" do |push|
>>>>>   #   push.app = "YOUR_ATLAS_USERNAME/YOUR_APPLICATION_NAME"
>>>>>   # end
>>>>>
>>>>>   # Enable provisioning with a shell script. Additional provisioners
>>>>> such as
>>>>>   # Puppet, Chef, Ansible, Salt, and Docker are also available. Please
>>>>> see the
>>>>>   # documentation for more information about their specific syntax and
>>>>> use.
>>>>>   # config.vm.provision "shell", inline: <<-SHELL
>>>>>   #   apt-get update
>>>>>   #   apt-get install -y apache2
>>>>>   # SHELL
>>>>>   Vagrant.configure("2") do |config|
>>>>>     config.vm.provider :libvirt do |libvirt|
>>>>>       libvirt.storage :file, :size => '8G', :type => 'raw'
>>>>>     end
>>>>>   end
>>>>> end
>>>>>
>>>>>
>>>>> Vagrant stále nenabíhá: "Error while creating domain: Error saving the
>>>>> server: Call to virDomainDefineXML failed: internal error: no supported
>>>>> architecture for os type 'hvm'"
>>>>>
>>>>> Dne 12. května 2017 14:32 Matěj Koudelka <matej at hxpro.cz> napsal(a):
>>>>>
>>>>> Tož v tom návodu se píše:
>>>>>>
>>>>>> Vagrant.configure("2") do |config|
>>>>>>   config.vm.provider :libvirt do |libvirt|
>>>>>>     libvirt.storage :file, :size => '20G'
>>>>>>     libvirt.storage :file, :size => '40G', :type => 'raw'
>>>>>>   end
>>>>>> end
>>>>>>
>>>>>> takže bych zkusil :type => ''raw'
>>>>>>
>>>>>>
>>>>>> Dne 12. května 2017 14:05 Petr Parolek <petr.parolek at gmail.com>
>>>>>> napsal(a):
>>>>>>
>>>>>> Nechce mi naběhnout virtuální stroj, vagrant píše:
>>>>>>>
>>>>>>> "==> default: Uploading base box image as volume into libvirt
>>>>>>> storage...
>>>>>>> ==> default: Creating image (snapshot of base box volume).
>>>>>>> Volume for domain is already created. Please run 'vagrant destroy'
>>>>>>> first."
>>>>>>>
>>>>>>> V KB vpsfree se píše, že se mají používat raw image pro hdd.
>>>>>>>
>>>>>>> Použil jsem tento návod https://github.com/vagrant-lib
>>>>>>> virt/vagrant-libvirt#installation.
>>>>>>>
>>>>>>> Nechtěl se mi stále spustit, řval, že mu chybí libvirt provider.
>>>>>>> Našel jsem:
>>>>>>>
>>>>>>> https://github.com/vagrant-libvirt/vagrant-libvirt/issues/77
>>>>>>> 0#issuecomment-298017815
>>>>>>>
>>>>>>> Zkompiloval jsem a nainstaloval providera aháže mi to chybu viz
>>>>>>> výše. Jak mám změnit nastavení storage u vagrantu?
>>>>>>>
>>>>>>> Díky moc za pomoc.
>>>>>>>
>>>>>>> Dne 12. května 2017 12:35 Petr Parolek <petr.parolek at gmail.com>
>>>>>>> napsal(a):
>>>>>>>
>>>>>>> Právěže znám. Naistaloval jsem si runner do Vagrantu u sebe na pc.
>>>>>>>> Díky moc za tip, nepadlo mě dát vagrant i na vps.
>>>>>>>>
>>>>>>>> Dne 12. května 2017 12:32 Matěj Koudelka <matej at hxpro.cz>
>>>>>>>> napsal(a):
>>>>>>>>
>>>>>>>> Znáš vagrant? Plugin vagrant-libvirt to umí s kvm. Na vps jsem to
>>>>>>>>> sice nezkoušel, ale na lokále to používám běžně. Nemusíš se pak vůbec
>>>>>>>>> připojovat na vnc a virtuálku máš rozchozenou raz dva. Stejně tak se pak
>>>>>>>>> můžeš do virtuálky dostat příkazem vagrant ssh.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Dne 12. května 2017 12:22 Petr Parolek <petr.parolek at gmail.com>
>>>>>>>>> napsal(a):
>>>>>>>>>
>>>>>>>>> Instalace OS do KVM je strašně pomalá přes VNC. Instalaci po
>>>>>>>>>> dlouhém čekání jsem instalaci Debianu vzdal, ani potom nevím, jak se
>>>>>>>>>> připojit k ssh z hosta do guesta tj. jak nastavit přesměrování portu.
>>>>>>>>>>
>>>>>>>>>> Dne 12. května 2017 9:53 Silvestr Hašek <hasek at reklalink.cz>
>>>>>>>>>> napsal(a):
>>>>>>>>>>
>>>>>>>>>>> Ahoj,
>>>>>>>>>>>
>>>>>>>>>>> Na netu jsou po různu issues s podobným bugem a co jsem viděl
>>>>>>>>>>> tak problém byl asi docker spousta hlašení na 1.10 a žádný řešení. Osobně
>>>>>>>>>>> bych doporučil uštípnout si kousek resources a udělat si malou vpsku s KVM,
>>>>>>>>>>> kde by ti měl odpadnout problém se starým dockerem. Gitlab máš vlastní
>>>>>>>>>>> instanci CE, takže k tomu asi ani nebudeš potřebovat další IPv4 kvuli tomu
>>>>>>>>>>> pitomýmu cloudu kde to mají hostovaný.
>>>>>>>>>>>
>>>>>>>>>>> Pokud nechceš stěpit vpsfree resources tak buď mít runner na
>>>>>>>>>>> developer mašinách nebo na to úplně stačí VPSka od nejmenované společnosti
>>>>>>>>>>> za 25Kč/Měsíc kde jde provozovat novější verze dockeru.
>>>>>>>>>>>
>>>>>>>>>>> On Friday, 12 May 2017 00:20:10 CEST, Petr Parolek wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Ahoj,
>>>>>>>>>>>>
>>>>>>>>>>>> tak ani z syslogu nejsem moudrý:
>>>>>>>>>>>>
>>>>>>>>>>>> https://pastebin.com/kvxdxrej
>>>>>>>>>>>>
>>>>>>>>>>>> Zatím to řeším workaroundem tak, že mám na svém pc ve vagrantu
>>>>>>>>>>>> puštěný
>>>>>>>>>>>> GitLab CI runner, který pouští buildy z mého gitlabu. Ale rád
>>>>>>>>>>>> bych měl vše
>>>>>>>>>>>> na VPS nezávisle.
>>>>>>>>>>>>
>>>>>>>>>>>> Má někdo nějaký nápad na řešení?
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Petr
>>>>>>>>>>>>
>>>>>>>>>>>> Petr
>>>>>>>>>>>>
>>>>>>>>>>>> 2017-05-08 15:21 GMT+02:00 Petr Parolek <petr.parolek at gmail.com
>>>>>>>>>>>> >:
>>>>>>>>>>>>
>>>>>>>>>>>> Ahoj, už delší dobu se potýkám s problémy při spouštění testů.
>>>>>>>>>>>>> Používám
>>>>>>>>>>>>> GitLab 9.1.2 CE s GitLab CI 9.0.4 a Docker 1.10.3 (tj.
>>>>>>>>>>>>> nejnovější Docker,
>>>>>>>>>>>>> který na VPSFree jede).
>>>>>>>>>>>>>
>>>>>>>>>>>>> Build často spadne s chybou: "ERROR: Preparation failed:
>>>>>>>>>>>>> Cannot connect
>>>>>>>>>>>>> to the Docker daemon at unix:///var/run/docker.sock. Is the
>>>>>>>>>>>>> docker daemon ...
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> Community-list mailing list
>>>>>>>>>>> Community-list at lists.vpsfree.cz
>>>>>>>>>>> http://lists.vpsfree.cz/listinfo/community-list
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> _______________________________________________
>>>>>>>>>> Community-list mailing list
>>>>>>>>>> Community-list at lists.vpsfree.cz
>>>>>>>>>> http://lists.vpsfree.cz/listinfo/community-list
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> *Matěj Koudelka*
>>>>>>>>> +420 604 266 933 <604%20266%20933>
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> Community-list mailing list
>>>>>>>>> Community-list at lists.vpsfree.cz
>>>>>>>>> http://lists.vpsfree.cz/listinfo/community-list
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Community-list mailing list
>>>>>>> Community-list at lists.vpsfree.cz
>>>>>>> http://lists.vpsfree.cz/listinfo/community-list
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> *Matěj Koudelka*
>>>>>> +420 604 266 933 <604%20266%20933>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Community-list mailing list
>>>>>> Community-list at lists.vpsfree.cz
>>>>>> http://lists.vpsfree.cz/listinfo/community-list
>>>>>>
>>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> Community-list mailing list
>>>> Community-list at lists.vpsfree.cz
>>>> http://lists.vpsfree.cz/listinfo/community-list
>>>>
>>>>
>>>
>>>
>>> --
>>> *Matěj Koudelka*
>>> +420 604 266 933 <604%20266%20933>
>>>
>>> _______________________________________________
>>> Community-list mailing list
>>> Community-list at lists.vpsfree.cz
>>> http://lists.vpsfree.cz/listinfo/community-list
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.vpsfree.cz/pipermail/community-list/attachments/20170512/0ac12936/attachment-0002.html>

More information about the Community-list mailing list