ykokw.xyz blog logo

Blog Posts

No results for 'undefined'Powered by Algolia
  • 成果物が こちら

    • snapshotと画面サイズ変更は手動でやるのが早そう。
  • cloudツール使うのでもいいけど、一度デプロイが必須になってしまうのがね

    • って思ったけどngrok使えばよさげ。。。?
    • browserstackからngrokのURLたたけばよさそう

やったこと

$ vagrant up --provider=virtualbox
The provider 'virtualbox' that was requested to back the machine
'default' is reporting that it isn't usable on this system. The
reason is shown below:

Vagrant has detected that you have a version of VirtualBox installed
that is not supported by this version of Vagrant. Please install one of
the supported versions listed below to use Vagrant:

4.0, 4.1, 4.2, 4.3, 5.0, 5.1, 5.2, 6.0

A Vagrant update may also be available that adds support for the version
you specified. Please check www.vagrantup.com/downloads.html to download
the latest version.
  • vagrant up が失敗した

    • dockerで立ち上げてたローカル環境と競合するポートをポートフォワーディング設定しているからだった
    • ゲストOSからホストOSへのアクセスにはポートフォワーディング関係ない(ホスト側=dockerで起動したサービスのポートとか)ので適当に設定した
$ vagrant up --provider=virtualbox
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'win10_edge'...
==> default: Matching MAC address for NAT networking...
==> default: Setting the name of the VM: vagrant-windows-box_default_1578035475082_4612
Vagrant cannot forward the specified ports on this VM, since they
would collide with some other application that is already listening
on these ports. The forwarded port to 10080 is already in use
on the host machine.

To fix this, modify your current project's Vagrantfile to use another
port. Example, where '1234' would be replaced by a unique host port:

  config.vm.network :forwarded_port, guest: 80, host: 1234

Sometimes, Vagrant will attempt to auto-correct this for you. In this
case, Vagrant was unable to. This is usually because the guest machine
is in a state which doesn't allow modifying port forwarding. You could
try 'vagrant reload' (equivalent of running a halt followed by an up)
so vagrant can attempt to auto-correct this upon booting. Be warned
that any unsaved work might be lost.
  • デフォルトがnat接続だったら、ホストOS経由でゲストOSもネットにアクセスできる

    • その状態であればIE開いて http://10.0.2.2:10080 とかで開くと、ホストOS側(dockerとか)で構築しているサービスにアクセスできる

その他

参考


This content is built with Gatsby