Nicolas De loof
Nicolas De loof
Thanks for investigating this Would probably be better for plugin to rely on new `Mounts` API to define bindings, and at least to offer a cleaner UI to define them....
Compared to #25 I can't see user set when `docker exec` is ran, which will cause issues with file permissions on workspace.
LGTM @antoniobeyah I would have expected the docker custom build environment plugin to provide `.inside` extension do docker-pipeline, and avoid such code duplication :-\ anyway, imho docker+jenkins future is [docker-slaves-plugin](https://wiki.jenkins-ci.org/display/JENKINS/Docker+Slaves+Plugin).
@antoniobeyah need to wait for plugin maintainer (@jglick)
@jglick both rely on `docker exec` a very comparable way, I don't see any reason they don't share a common code base.
could probably be addressed once https://github.com/jenkinsci/docker-plugin/issues/549 is done
Relying on image is also a bad option, as one might have mulitple templates based on same image, but distinct constraints (for sample, a "M" template with max memory=200M and...
sounds good. I gave up with JENKINS-48050 as I can't imagine a reasonable solution as long as we have to live with a Java based remoting agent, so feel free...
created default.yaml file with updated ` loadDotSSHPubKeys: false` ``` $ limactl start default.yaml ... INFO[0598] [hostagent] Waiting for the essential requirement 1 of 4: "ssh" FATA[0607] did not receive an...
added a test case to inspect a docker app of mine pushed as OCI index list on docker hub