Matti Paksula
Matti Paksula
export PROMPT_COMMAND='history -a' "solves" this history thing, this way bash writes the history after every command and not just at the end.
I think what happened was that the pod was in creation and then the updates were stale (again) and therefore the exec (shell) wasn't there. And a sidenote: I think...
"OMG SOME NODES HAVE FULL DIS..... oh, Lens"
similar to https://github.com/docker/for-mac/issues/1667
I can confirm that I have exactly same setup like @tomlau10 and it started to fail every other time in github actions
a sample of ec2-instance-selector that I'm using to get the list I want. I can not use eksctl built-in ec2-instance-selector as it's bare bones and doesn't support all filtering options...
error out instead as I am requesting things that can not be fulfilled
now the behaviour is imo unexpected as it "silently" (unless I follow the logs) removes an AZ from what I'm expecting.
@Utherellus I'm going to sidetrack a bit, but what is the reason that you want to run this game in a vm? to keep host windows clean? other reasons?
same here, tried doing simplest hello world