FlorianS

Hello guys, I encountered the bug also even when using the example script https://github.com/npalm/terraform-aws-gitlab-runner/blob/develop/bin/cancel-spot-instances.sh I saw it during destroy but it can occurs while updating ASG too , there is...

If it can help, I push #359 which is the result of multiple tests. It does not solve fully the issue but note that you have to think about removing...

It look like the container executed only upload to S3 files with filename appearing in JMX file. https://github.com/awslabs/distributed-load-testing-on-aws/blob/849b9a92e4c03545cd775005bb925bb7085c679c/source/container/load-test.sh#L59-L75 I have an `urls.csv` file for my execution and the JMX config...

How did you give access to the`http_proxy` `https_proxy` vars for buildkit in the end ? @nichoio

Found it ! Just add `--opt build-arg:myvar=myvar` Here is my resulting code in my case ```bash buildctl-daemonless.sh build --frontend dockerfile.v0 --local context=. --local dockerfile=. --output type=image,name=${DOCKER_IMAGE_NAME}:${BUILD_VERSION},push=${ECR_PUSH} ${BUILDKITD_EXTRA_ARGS} --opt build-arg:http_proxy=${http_proxy} --opt...