Giter VIP home page Giter VIP logo

fedora's People

Contributors

andreabedini avatar annawake avatar berendt avatar bertvv avatar dol avatar florianmaier101178 avatar jmartin-tech avatar marun avatar mgruner avatar misheska avatar olberger avatar pslattery avatar pysis868 avatar rasa avatar rickard-von-essen avatar robertdebock avatar sandra-thieme avatar tas50 avatar taylorific avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

fedora's Issues

vboxsf doesn't work for Vagrant shared folders on Fedora 28 workstation

As mentioned in #35 I think the rebuild of the VirtualBox Guest extensions modules doesn't work, which leads to vboxsf not operational when doing a vagrant up.

I haven't tested after the merge from today, but that's what I get with the fedora28-ws variant on the patrickmslatteryvt origin's tree.

There are quite a number of posts out there mentioning issues with vbox guest extensions recompilation on Fedora28, but I haven't found a definitive reference.

Hth

Fedora Workstation.

Why are there now workstation boxes in the repository?
The ubuntu repository has Desktop with GUI enabled.

Private network

Hi.
I'm trying to create private network for vApp.
Currently, my vagrant file looks like this:

# -*- mode: ruby -*-
# vi: set ft=ruby :

nodes = [
  { :hostname => 'gateway',
    :box => 'valor-scada-f20-v12',
    :box_url => "file:///home/dheinisc/Dev/valor-scada-f20-v12-vcloud.box",
    :ip => "10.0.0.10"},
  { :hostname => 'line',
    :box => 'valor-scada-f20-v12',
    :box_url => "file:///home/dheinisc/Dev/valor-scada-f20-v12-vcloud.box",
    :ip => "10.0.0.11"},
  { :hostname => 'process1',
    :box => 'valor-scada-f20-v12',
    :box_url => "file:///home/dheinisc/Dev/valor-scada-f20-v12-vcloud.box",
    :ip => "10.0.0.12" },
]

Vagrant.configure('2') do |config|

  config.vm.provider :vcloud do |vcloud|

    vcloud.hostname = 'vcloud_url'

    vcloud.username = 'user'
    vcloud.password = 'password'
    vcloud.org_name = 'Org name'
    vcloud.vdc_name = 'vDC name'
    vcloud.catalog_name = 'catalog name'
    vcloud.network_bridge = false             

    # Set the Organization Network where we will attach our vApp to
    vcloud.vdc_network_name = 'network name'
  end

  nodes.each do |node|
    config.vm.define node[:hostname] do |node_config|
      node_config.vm.box = node[:box]
      node_config.vm.hostname = node[:hostname]
      node_config.vm.box_url = node[:box_url]
      node_config.vm.network :private_network, ip: node[:ip]
      node_config.vm.network :forwarded_port,
                             guest: 80,
                             host: 8080,
                             auto_correct: true
    end
  end
end

The following is the vApp diagram:
image

What i'm expecting is that the VMs inside the vApp will have private network (vApp network) with ip: 10.0.0.X

Also, my vApp template has 6 NICs and when i use vCloud GUI to create VM i see that the VM contains 6 NICs (by using ifconfig).
When i use vagrant-vcloud with the same vApp template, the VM is created with single NIC and it's network is: Vagrant-vApp-Net.
Why? Where this network is coming from?
Why all the other NICs are removed?

Please assist.
Thanks in advance, Dor.

virtualbox guest not installed on Fedora 22

I used vagrant init box-cutter/fedora22; vagrant up --provider virtualbox to install the vm and I have VirtualBox-5.0-5.0.2_102096_fedora22-1.x86_64 installed on my host. But if I vagrant ssh into the box and do lsmod I don't see any vbox* modules loaded.

I can try building the image myself from the repo but I wanted to open an issue to let you know and track progress.

Add cleanup of unused kernels

cleanup.sh should include removal of the kernels no longer needed (initial kernel before updates).

For fedora 28, that'd be:
dnf remove -y $(dnf repoquery --installonly --latest-limit=-1 -q)

Hth,

reboot in update.sh kills virtualbox.sh provisionning script for fedora28

Maybe this is due to some change with the fedora28 provisionning, but I've noticed that the virtualbox.sh doesn't run completely, and gets killed by the VM rebooting.

I suspect this is caused by the reboot that is made at the end of update.sh (and is required whenever the Kernel changes).

Anyone experienced this too ?

Vmware Fedora 22: Waiting for HGFS kernel module to load takes endlessy

Hello, currently I created a VM with boxcutter/fedora and packer.io and somehow starting the vm with vagrant up hangs on:

==> default: Waiting for HGFS kernel module to load...

and after a while there is

The HGFS kernel module was not found on the running virtual machine.
This must be installed for shared folders to work properly. Please
install the VMware tools within the guest and try again. Note that
the VMware tools installation will succeed even if HGFS fails
to properly install. Carefully read the output of the VMware tools
installation to verify the HGFS kernel modules were installed properly.

Looks like the patch is just too old

Add cleanup of kernel devel/header packages

The kernel devel and header packages aren't necessary in general, passed the point of rebuilding the Virtualbox Guest Extensions.

Removing these packages should lead to thiner box

VM with multiple NICs

Hi.
I am using vagrant vcloud in order to deploy VM with multiple network cards interface.
The vApp template contains VM which has 6 NICs.
When creating a vApp out of this vApp template manually (by using vcloud GUI) i get a VM with 6 NICs.
When using vagrant-vcloud, the VM has a single NIC even though its the same vApp template i mentioned above.

Please advise,
Thanks in advance,
Dor.

Fedora 24 Download Fails

Hello,
While trying to use the new boxcutter/fedora24 Vagrant box, I get the following error:

Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'boxcutter/fedora24' could not be found. Attempting to find and install...
    default: Box Provider: virtualbox
    default: Box Version: >= 0
==> default: Loading metadata for box 'boxcutter/fedora24'
    default: URL: https://atlas.hashicorp.com/boxcutter/fedora24
==> default: Adding box 'boxcutter/fedora24' (v3.0.3) for provider: virtualbox
    default: Downloading: https://atlas.hashicorp.com/boxcutter/boxes/fedora24/versions/3.0.3/providers/virtualbox.box
An error occurred while downloading the remote file. The error
message, if any, is reproduced below. Please fix this error and try
again.

The requested URL returned error: 403 Forbidden

Thanks for your help.

Fedora25 is 404

I used fedora 24.
I tried updating to fedora 25.
But I could not download fedora 25.

The box 'boxcutter/fedora25' could not be found or
could not be accessed in the remote catalog. If this is a private
box on HashiCorp's Vagrant Cloud, please verify you're logged in via
`vagrant login`. Also, please double-check the name. The expanded
URL and error message are shown below:

URL: ["https://vagrantcloud.com/boxcutter/fedora25"]
Error: The requested URL returned error: 404 Not Found

Thanks for your help.

Fedora 24

Hello,

Fedora 24 was released yesterday. I would appreciate it if a Fedora 24 box was released soon.

Thanks for your effort!

Upgrade for F28

In case anyone is interested in Fedora 28 support ?

I may have something working soon... unless someone beats me and forgot to push ;)

Private networks not working

At the moment it is not possible to use private networks with this box (Fedora 21) and current Vagrant.

==> default: Configuring and enabling network interfaces...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

ARPCHECK=no /sbin/ifup eth1 2> /dev/null

Stdout from the command:

ERROR    : [/etc/sysconfig/network-scripts/ifup-eth] Device eth1 does not seem to be present, delaying initialization.


Stderr from the command:
[vagrant@openstack ~]$ ip a s
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp0s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 08:00:27:03:50:41 brd ff:ff:ff:ff:ff:ff
    inet 10.0.2.15/24 brd 10.0.2.255 scope global dynamic enp0s3
       valid_lft 86274sec preferred_lft 86274sec
    inet6 fe80::a00:27ff:fe03:5041/64 scope link 
       valid_lft forever preferred_lft forever
3: enp0s8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 08:00:27:61:ad:8d brd ff:ff:ff:ff:ff:ff
    inet6 fe80::a00:27ff:fe61:ad8d/64 scope link 
       valid_lft forever preferred_lft forever

In dmesg:

[    4.571002] e1000 0000:00:08.0 enp0s8: renamed from eth1
[    4.658664] e1000 0000:00:03.0 enp0s3: renamed from eth0
[vagrant@openstack ~]$  ll /etc/sysconfig/network-scripts/ifcfg-*
-rw-r--r-- 1 root root 168 Apr 14 09:54 /etc/sysconfig/network-scripts/ifcfg-enp0s3
-rw-r--r-- 1 root root 633 Apr 14 09:54 /etc/sysconfig/network-scripts/ifcfg-eth1
-rw-r--r-- 1 root root 254 Apr 14 09:54 /etc/sysconfig/network-scripts/ifcfg-lo

Makefile.local:

CM := nocm
HEADLESS := true
UPDATE := true
PACKER := /opt/packer/packer
PACKER_DEBUG := true

Vagrantfile:

...
config.vm.network :private_network, ip: '10.25.25.25'
...
% vagrant version
Installed Version: 1.7.2
Latest Version: 1.7.2

You're running an up-to-date version of Vagrant!

Missing Fedora 27

The current release includes Fedora 25 (default) and Fedora 26 but 27 is missing.

I'll make a merge request after testing that includes Fedora 27.

Maybe it's also good to use Fedora 27 as the default, I'll not include that in the merge request though.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.