Mathias Brodala

Alternatively the logic to import static data could be executed again after truncating all tables.

I just set up the metrics-server with the [`components.yaml` from the v0.3.6 release](https://github.com/kubernetes-sigs/metrics-server/releases/tag/v0.3.6) and made sure to inject the `--kubelet-preferred-address-types=InternalIP` flag as mentioned here. (Using kustomize and a JSON patch...

@timoreimann this is the original dashboard provided by DOKS.

This **should** be possible with [schema dependencies](http://spacetelescope.github.io/understanding-json-schema/reference/object.html#schema-dependencies) like this: ``` json { "type": "object", "properties": { "name": { "type": "string" }, "credit_card": { "type": "number" } }, "required": ["name"], "dependencies":...

Sure but as mentioned this is about a general solution, not some workaround. ;-)

`push` could maybe start with the component root path in `/data/var` if no absolute file path is provided. Thus `nanobox push data.storage foo.txt` would automatically store in `/data/var/db/unfs/foo.txt` within the...

It would also be useful if this could be applied to containers in a more general sense. An example for the `mysql` component: ``` nanobox pull data.mysql ``` This could...

I get the same issue when issuing a `nanobox run test.php` locally so I guess something's wrong with my `boxfile.yml`? ```yaml run.config: engine: php engine.config: runtime: php-7.0 web.site: {} ```

Alright, the issue seems to be gone today. I did perform a `nanobox-update` and `nanobox update-images` though.

See [this build log](https://app.shippable.com/bitbucket/mbrodala/shippable-nanobox/runs/9/1/console) for details. And the [repository source](https://bitbucket.org/mbrodala/shippable-nanobox/src).