RichardScottOZ

I did not change any defaults from anything and default python3 - does installing status mean it is expecting a container called python3? I definitely do not have a runtime...

Next test for timeout problems then I guess it to make a simple image or something along those lines.

try redoing the default and see what happens?

When I try that ```LAUNCH SPECIFICATION: {'ImageId': 'ami-004dac467bb041dc7', 'InstanceType': 't3.medium', 'EbsOptimized': False, 'IamInstanceProfile': {'Name': 'ec2LithopsInstanceRole'}, 'Monitoring': {'Enabled': False}, 'KeyName': 'lithops-key-b597095a', 'NetworkInterfaces': [{'AssociatePublicIpAddress': True, 'DeviceIndex': 0, 'SubnetId': 'subnet-0e2cc6c50620ea4c6', 'Groups': ['sg-09debf19a006a85f1']}], 'BlockDeviceMappings':...

so how to get this ```python def is_ready(self): """ Checks if the VM instance is ready to receive ssh connections """ login_type = 'password' if 'password' in self.ssh_credentials and \...

again though it looks like it has made it - in the console 

and if I disable the error handling in the above ```python timed out Traceback (most recent call last): File "/home/richard/miniconda3/envs/lithops/bin/lithops", line 8, in sys.exit(lithops_cli()) File "/home/richard/miniconda3/envs/lithops/lib/python3.10/site-packages/click/core.py", line 1157, in __call__...

which could be unintended consequence of my tinkering to get some other private_ip things to work?

so failing to create a ssh_client on the run_remote part above not sure why failing to connect to these build machines when others are ok as far as ssh connection...

I can definitely connect manually to a build-* machine anyway via the private ip so not sure why code is failing here.