Yossi Cohn
Yossi Cohn
> It would be useful to be able to mount a directory (even just the build context) to make it accessible within the Dockerfile. > This is obviously possible when...
@sposten I had an issue with ssh mounting. You can see here what I have done. https://link.medium.com/nnEY55BIolb
@crenshaw-dev @ftsell from what I see when using a proxy (LB and k8s ingress resource) I get the CSP error and I guess it relates to what you are discussing...
We also had this over v3.5.2...the solution was to restart the controller. It does mean we have a major issue with the workflows using the `Mutex` feature. Does a `Semaphor`...
Just got the same error on the same COPY issue ``` COPY /source/* target/ ```
We have the same issue, seems like a regression after upgrading to `v1.34.0.` (upgraded from `v1.32.2` where everything runs well) We run on `k8s` and we get `Error: open /usr/lib/containers/storage/overlay-images/images.lock:...
@zmjackson just changed the security context from ``` container: securityContext: allowPrivilegeEscalation: false runAsUser: 1000 runAsGroup: 1000 capabilities: drop: - ALL ``` to ``` securityContext: priviledged: true ``` and it worked...but...
@zmjackson what do you think about that ^^ any ideas how we can proceed?
@sylvainpelletier thanks, is there a reason for the `storage.conf ` to be added, is there a way to have the previous behaviour like at 1.27 ?
@JeromeJu the latest I know of working is v1.12.0, in the process of upgrade to the latest I got all the issues of the COPY I mentioned above