Alex Couture-Beil

This appears to work: ``` VERSION 0.6 FROM alpine:3.13.6 ENV key value RUN env | grep key ``` ``` $ earthly-v0.6.8 --no-cache +base 1. Init 🚀 ———————————————————————————————————————————————————————————————————————————————— buildkitd | Found...

> It also doesn't work without quotes :) Looks like this is a valid Dockerfile :exploding_head: (surprising since bash doesn't allow exporting envs with a hyphen) ```Dockerfile FROM alpine:3.13.6 ENV...

I would be curious to know what `df` sees inside earthly: ```Earthfile df: FROM alpine RUN --no-cache df -h ``` on my system I end up with: ``` +df |...

I'm a bit stumped; I have two ideas: 1) Could it be that after the failure is detected, that the snapshot is deleted? I wonder if you can run `earthly...

Currently it's possible to work-around this bug with: ```Earthfile VERSION --shell-out-anywhere 0.6 test: FROM alpine WORKDIR /the-test RUN --mount=type=cache,target=$(echo $HOME)/hello find / | grep hello ``` which would correctly produce...

in bash, single quotes will take it as a literal string; for example: ``` $ echo '$(date +%s)' $(date +%s) $ echo "$(date +%s)" 1593472152 ``` we should have earthly...

https://github.com/earthly/earthly/issues/86#issuecomment-651415230 outlines the behaviour we want: single-quotes should work as they do in bash -- they shouldn't allow shelling-out or variable substitution.

> we can add 2 new parameters in lex configuration (say processSingleQuote and processDoubleQuote) and set these parameters according to command we want to process in earthly code It could...

> Is there a reason why the system's file (/etc/ssh/ssh_known_hosts) is not used as a source of keys? I think this is an oversight, if it exists we should pull...

#1795 implements reading from `/etc/ssh/ssh_known_hosts`