Hello,

with yum info audit I can confirm that the package audit is installed.
with rpm -ql audit I can see a list of files, including /usr/share/doc/audit-2.3.7/*
But those files are missing
ls: cannot access /usr/share/doc/audit-2.3.7: No such file or directory

CentOS 6.7
Can you help with that?
Thanks.

• I've read the guidelines for Contributing to Roots Projects
• This request isn't a duplicate of an existing request
• This is not a personal support request that should be posted on the Roots Discourse community

Feature request

When re-provisioning a server with a users tag `trelli

What are you trying to do?
I would like to be able to use a cloud-init.yml from a url while launching a new vm

multipass launch -n test -c 2 --cloud-init http://my-home.com/multipass/cloud-init.yml

What's your proposed solution?
--cloud-init should support http:// files

Additional context
Add any other context or screenshots about the feature request here.

Invoking:

nanobox configure set mount-type foo

Outputs this (with an exist code of 0):

Successfully set 'mount-type'

However the value remains whatever it was before. If you enter a valid value it works of course.

Was expecting it to error out if unknown mount type.

环境：

• Mac
• vagrant 2.1.2
• virtualBox: 5.2.16
• Kubernetes 1.11.0

遇到了几个问题：

1. 在系统自动挂起之后vm 的时间会不对，没有自动同步，导致 Prometheus 监控数据显示不出来，应该同步时间就可以，不过我没有，而是使用的 vagrant halt ，就导致了另一个问题。
2. 执行 vagrant halt 按照【重启】 的操作后，之前配置的 Istio 相关所有东西都不见了，包括 istio-system namespace 。
3. 按照[文档](

Issue Type

• Feature Idea

Summary

I would like to use GoAccess as a dev tool instead of PimpMyLog. How can I go about setting it up automatically when I create a new VM?

When using the box built with osx-vm-templates, there is always some setting to tune in upper Vagrantfile.

Can we built those common settings into box with vagrantfile_template

There is a good [reference here](https://github.com/blueimp/boot2docker/blob/b33c71d07f2cfdc94e6f9150793bbb47a78f6b70/packer.jso

To Reproduce
Steps to reproduce the behavior:

1. Run make all as described in README.md and follow install process.
2. After install, macOS-VM.efi.vdi and macOS-VM.vdi are located directly in ~/VirtualBox VMs instead of ~/VirtualBox VMs/macOS-VM as is typical for VirtualBox VMs.

Expected behavior
After install, macOS-VM.efi.vdi and macOS-VM.vdi should be located in `~/

I don't find mention of how to install plugins in the README or the docs linked from there.

Assuming most new nixops users are going to want to try nixops with libvirtd or VirtualBox, this is a significant adoption blocker.

In addition to CPU and memory, it would be useful to be able to specify the amount of VRAM, since the default value (at least for Parallels) is quite low.

It should be fairly straightforward to implement, again, for Parallels it would be:

prl.customize ["set", :id, "--videosize", "256"]

This would set VRAM to 256 MB.

Actual:
xdebug.max_nesting_level is set to 200 but default is 256 and even 256 is not enough for some scenarios.

Expected:
xdebug.max_nesting_level is set to 256 by default. Documentation reflects the possibility of issues with nesting level setting and describes the workaround.

More details: https://jira.corp.magento.com/browse/MC-5828

the following steps from the manual haven't been done during the multiserver (expert) installation, using the auto install script.

OS. debian 9

mkdir /opt/certbot
cd /opt/certbot
wget https://dl.eff.org/certbot-auto
chmod a+x ./certbot-auto