Ky-Anh Huynh

@ckyoog I've tried your patch, but then the command `git status` always failed, then I couldn't lock/unlock and/or do anything. I had to disable the extension, use `lock -force` and...

> @icy you may be using and old git client that doesn't support `--worktree`, i.e. if `git config --worktree` fails, the patched `git-crypt` will be failing as well. Also try...

@ckyoog I have the issue with (hopefully) new git as below ``` $ git worktree add -b testing w/test Preparing worktree (new branch 'testing') git-crypt: Error: Unable to open key...

> could you try moving the filters from .git/config to .git/config.worktree Thanks a lot. My mistake, I should have executed `git lock` before executing `git worktree`. I confirm @ckyoog's patch...

@yxliang01 `ARG` is a new instruction that wasn't available when I started to write Bocker (IMHO). Is that similar to `ENV` but that's only used at build-time? Is there any...

@yxliang01 I got it. thx for your explanation. The primary movitation of Bocker is to enclose (almost) everything by using Bash routines. It's pretty not easy to do/understand this at...

A real example for btsync image: https://github.com/icy/docker/blob/master/bocker/Bockerfile.btsync14

@yxliang01 :) it's ok. I will have support for `ARG` quickly. It's almost the same as `LABEL` so you may take a look. Btw, maybe you help to test if...

I know there are many short `Dockerfiles`, but as serious shell (Bash) user I really dislike some ideas in Dockerfile syntax. And, I believe that Dockerfile should/can be generated (this...

An initial work is on `cap` branch (https://github.com/icy/bocker/tree/cap), but it doesn't really help. It just creates more confusion https://github.com/icy/bocker/blob/cap/examples/Bockerfile.minimal.cap