Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

some CI fails because of vagrant shared folder configuration #593

Closed
kenhys opened this issue Oct 16, 2023 · 3 comments
Closed

some CI fails because of vagrant shared folder configuration #593

kenhys opened this issue Oct 16, 2023 · 3 comments

Comments

@kenhys
Copy link
Contributor

kenhys commented Oct 16, 2023

Problem

When checking #592 CI action, it was observed that
testing CI failure.

==> debian-bullseye: Matching MAC address for NAT networking...
==> debian-bullseye: Checking if box 'bento/debian-11' version '202309.08.0' is up to date...
==> debian-bullseye: Setting the name of the VM: fluent-package-builder_debian-bullseye_1697186282329_19143
Vagrant is currently configured to create VirtualBox synced folders with
the `SharedFoldersEnableSymlinksCreate` option enabled. If the Vagrant
guest is not trusted, you may want to disable this option. For more
information on this option, please refer to the VirtualBox manual:

  https://www.virtualbox.org/manual/ch04.html#sharedfolders

This option can be disabled globally with an environment variable:

  VAGRANT_DISABLE_VBOXSYMLINKCREATE=1

or on a per folder basis within the Vagrantfile:

  config.vm.synced_folder '/host/path', '/guest/path', SharedFoldersEnableSymlinksCreate: false
==> debian-bullseye: Clearing any previously set network interfaces...
==> debian-bullseye: Preparing network interfaces based on configuration...
    debian-bullseye: Adapter 1: nat
==> debian-bullseye: Forwarding ports...
    debian-bullseye: 22 (guest) => 2222 (host) (adapter 1)
==> debian-bullseye: Running 'pre-boot' VM customizations...
==> debian-bullseye: Booting VM...
==> debian-bullseye: Waiting for machine to boot. This may take a few minutes...
    debian-bullseye: SSH address: 127.0.0.1:2222
    debian-bullseye: SSH username: vagrant
    debian-bullseye: SSH auth method: private key
The guest machine entered an invalid state while waiting for it
to boot. Valid states are 'starting, running'. The machine is in the
'gurumeditation' state. Please verify everything is configured
properly and try again.

Expected

Above CI failure will be solved.

@kenhys kenhys changed the title some CI fails because of shared folder configuration some CI fails because of vagrant shared folder configuration Oct 16, 2023
@kenhys
Copy link
Contributor Author

kenhys commented Oct 17, 2023

At first, it seems that shared folder configuration is related, but it is not.(it is just example to disable it)
At least, it can't be reproduced on:

VBoxManage -v
7.0.10_Debianr158379
vagrant version
Installed Version: 2.3.4

It may be better to try on:

https://github.com/actions/runner-images/blob/main/images/macos/macos-12-Readme.md

@kenhys
Copy link
Contributor Author

kenhys commented Oct 17, 2023

==> debian-bullseye: Successfully added box 'bento/debian-11' (v202309.08.0) for 'virtualbox'!
==> debian-bookworm: Checking if box 'bento/debian-12' version '202309.08.0' is up to date...

It seems that both of image can not be booted with Vagrant 2.3.7, VirtualBox 6.1.38r153438 (See macos-12-Readme.md)

@kenhys
Copy link
Contributor Author

kenhys commented Dec 11, 2023

Fixed via #603

Now migrated to lxc.

@kenhys kenhys closed this as completed Dec 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant