Keming

> @Xuanwo Thanks for your fix! Probably you should try Grammarly. There are still some syntax errors.

Is there a bug in https://github.com/tensorchord/envd/blob/53d8e13fc3cf39cd8a1c38e80d411096dd99e234/pkg/builder/util.go#L321-L338 So no matter what you pass to `-f`, it will always use the default`build.envd`. (Unless you specify the target function) BTW, the `-f` description...

Some articles: - https://manjusaka.itscoder.com/posts/2021/02/13/a-simple-introduction-about-the-init-process-in-container/ - https://manjusaka.itscoder.com/posts/2021/02/27/damn-the-init-process/

* ping me when it's ready to review * I'm going to fix #446, this PR will make it easy (so I don't need to change both `up` and `build`

> No problem, I am working on it and wil have it fixed today. A headache happend to me yesterday. Take care and take your time, not an urgent task.

1. The keyword `load` is already in [`starlark`](https://github.com/google/starlark-go/blob/master/doc/spec.md#load-statements), I'm not sure if we want to override it. 2. I prefer to define some *internal* functions and load them before `config.envd`....

2. Plus, people can use use `git` to sync the files under `ENVD_PRELOAD_DIR` to make sure everybody in the team can share the same utilities.

I would recommend https://github.com/VictoriaMetrics/VictoriaMetrics as a way to store the metrics. But I'm still not very sure if all the metrics we need can be stored in a way like...

* Also related to #13

Requirements: * apt install fish * starship init fish * fish config (conda init if it's required)