José Alberto
José Alberto
To change file permission is very intrusive, I understand the need for something like this a couple of years ago, but now both in production (k8s has a way to...
My workaround in docker-compose: ``` user: root entrypoint: ["node", "current/index.js"] ``` this works fine with podman rootless
will be great to have linux support too, as rocm works in Linux
I am happy to test in a RX 7600
What about an intermediate solution with containers/kubernetes integration? So you will define which container image you want to run your code in, that way any code/command can be used.
Yes, thanks, I kind of missed it. By the docs it doesn't seem really integrated, (will be lovely to manage the containers state, cpu, mem, etc without scripting it each...
As a workaround I just edited the template. Main reason to use V3 is not to upgrade later :)
As a suggestion, why not just to use latest version available in whatever Azure region is being use? so user selects D2 and it detects in current region latest version...
is there any workaround to achieve a similar goal?
@ddebroy that probably will work for some scenarios, but is less flexible, ie: - 2 envs: prod & staging - isolated by swarm netowrk - with periodic "syncs" (so you...