Question

编辑：似乎我所要做的就是等待。但我仍然想知道这个输出是否对人类有意义。

Windows 8.1主机。

我使用Git命令行界面代替cmd，所以我可以使用熟悉的linux CLI命令。我刚刚运行了以下两个命令，第一个命令运行没有错误，第二个命令似乎仍在执行某些操作：

$ vagrant init ubuntu/trusty64-juju
$ vagrant up

第一个命令发生得很快，没有错误。但是在第二个命令之后，虽然虚拟机已启动并在虚拟框中运行（我使用user / pass＆＃34; vagrant＆＃34;登录），但在Windows Git CLI中，我看起来像下面的无限输出。起初我想也许有些配置还在发生，所以我等了。但是30分钟后它还在继续。

==> default: :
==> default: 2
==> default: 9
==> default: :
==> default: 2
==> default: 3
==> default:
==> default:
==> default: 0
==> default: :
==> default: 0
==> default: 9
==> default: :
==> default: 0
==> default: 5
==> default:
==> default: 8
==> default: 8
==> default: 2
==> default: 1
==> default: 7

好的哇，几分钟后，似乎终于发生了一些事情：

==> default: 6
==> default: 3
==> default: k
==> default: Bootstrapping Juju...
==> default: Bootstrapping environment "local"
==> default: Starting new instance for initial state server
==> default: Building tools to upload (1.25.3.1-trusty-amd64)
==> default: Installing Juju agent on bootstrap instance
==> default: Logging to /home/vagrant/.juju/local/cloud-init-output.log on remote host
==> default: Installing package: curl
==> default: Installing package: cpu-checker
==> default: Installing package: bridge-utils
==> default: Installing package: rsyslog-gnutls
==> default: Installing package: cloud-utils
==> default: Installing package: cloud-image-utils
==> default: Installing package: tmux
==> default: Bootstrapping Juju machine agent
==> default: Starting Juju machine agent (juju-agent-vagrant-local)
==> default: Bootstrap agent installed
==> default: -> local
==> default: Waiting for API to become available
==> default: Waiting for API to become available
==> default: Waiting for API to become available
==> default: Bootstrap complete
==> default: Taking a nap to let state server come up...
==> default: Added charm "cs:trusty/juju-gui-48" to the environment.
==> default: Setting up Juju GUI dependencies...this may take a minute.
==> default: You can find the log in /var/log/juju-setup.log
==> default: You have not informed bzr of your Launchpad ID, and you must do this to
==> default: write to Launchpad or access private data.  See "bzr help launchpad-login".
==> default: Branched 25 revisions.
==> default: Taking a nap to let Juju Gui get setup
==> default:
==> default: Setting up transparent redirect for Juju-Gui
==> default: Redirecting localhost:6079 to 10.0.3.49:80
==> default:
==> default: Executing: sudo iptables -t nat -A PREROUTING -p tcp --dport 6079 -j DNAT --to 10.0.3.49:80
==> default:
==> default: From your browser on your hosts, you should be able to
==> default: access the GUI by going to: http://127.0.0.1:6080
==> default:
==> default: Your password is: mACsz/qM
==> default: juju-gui start/running, process 20170
==> default: juju-gui start/running, process 20170

我只是不了解那里的用户体验哲学，用户根本不知道发生了什么。我之前怎么理解那个输出？

Answer 1

这可能是由于盒子的作者要么a）以这种方式配置，要么b）不考虑你的设置特定的东西，这会把输出扔到你的终端（例如，他们可能希望盒子从POSIX环境而不是Windows Git CLI。

正如问题评论中所建议的那样，联系盒子所有者或选择其他方框有助于缩小问题范围。通常无问题地工作的常见框是由hashicorp（Vagrant的制造商）或标准和流行的ubuntu或debian框（例如ubuntu / trusty64）发布的。

＆＃34;流浪＆＃34;打印数百行以＆＃34; ==＆gt;开头默认值：＆＃34;

1 个答案: