Viacheslav Vasilyev
Viacheslav Vasilyev
unfortunately, provided workaround does not mount volumes to configurer pod, I'll try to take a look on array implementation after I finish with kvv2 check-and-set
it has failed on ```json { "timestamp": "1541758414.146682024", "source": "guardian", "message": "guardian.iptables-runner.command.failed", "log_level": 2, "data": { "argv": [ "/worker-state/4.2.1/assets/iptables/sbin/iptables", "--wait", "--table", "nat", "-A", "w--prerouting", "--jump", "w--instance-pbd2incpuj9", "-m", "comment", "--comment", "cdc24ff9-ad25-4fc8-6443-5c5ae9317b35"...
solved with docker downgrade
I agree, given the CVE-2019-5736 downgrade is not an option
@NewJorg what OS, kernel version it was?
I wasn't able to run Concourse CI with the latest boot2docker image, the version which has been working for me is: ``` https://github.com/boot2docker/boot2docker/releases/download/v18.06.1-ce/boot2docker.iso ``` @larssb which boot2docker version could you...
@dzirg44 suggested had helped me to solve the issue, don't forget to re-create docker-machine if you're mapping generated keys as volumes
really? two weeks and no answer?
more closest option is `--garden-network-pool`, but still it's different ``` --garden-network-pool= Network range to use for dynamically allocated container subnets. (default: 10.254.0.0/22) [$CONCOURSE_GARDEN_NETWORK_POOL] ```
if you don't mind I'll do PR #3