Convox Build Instance Documentation

Configuration
1

Hi all, I’ve got a build instance on AWS that I’d like to replace, but I can’t seem to find the documentation on build instances anymore. Does anyone have a link to the documentation?

Thanks!

2

Hey @cap

Can you give me some more information here? Is this a v2 or v3 rack? What exactly are you trying to accomplish when you mean replace it?

Regards,
Nick

3

Hi Nick, thanks for your reply. This is a v1 rack, I believe. I have a dedicated build instance and I’d like to destroy it and create a new dedicated build instance. I’m saying this because I tried to change the instance type but it doesn’t seem to work. I used this command:

convox rack params set BuildInstance=t4g.nano

and this was the response:

Updating parameters... OK

But nothing seems to be changing on the ec2 instance panel. My build instance is still of the old type (t2.nano). Subsequently, I tried to use this command:

convox rack params set BuildMemory=384

But was met with these messages. First:

Updating parameters... ERROR: ValidationError: Stack:arn:aws:cloudformation:us-redacted is in UPDATE_IN_PROGRESS state and can not be updated.
	status code: 400, request id: redacted

And later:

Updating parameters... ERROR: ValidationError: No updates are to be performed.
	status code: 400, request id: redacted

On this page, there is a link to a page for “dedicated build instance”:

But when I click on that link, it doesn’t have the dedicated build instance portion anymore:

When I try to terminate the build instance using convox instances terminate i-redacted, I get an error message that says: Terminating instance... ERROR: instance not found: i-redacted

5

Hi, I checked the web console and it says our rack is a v2 rack. Sorry, I mistakenly said it was a v1 rack above.

6

Hey @cap

My suspicion is that you’re attempting to set your build instance to an ARM-based instance (t4g.nano) while your primary instance type is x86. Both build and primary instance types must be on the same architecture.

So you should set these at the same time e.g.
convox rack params set InstanceType=t4g.nano BuildInstance=t4g.nano

The Build memory error is likely due to instance capacity. Attempting to pack the API 128MB and 384MB to build is likely still going to encounter problems due to basic system/container overhead.

If 384MB is a requirement for your build memory, you could try to lower the rack parameter ApiMemory some to help pack this instance as close as possible. But please be advised lowering these too much can cause connection issues to your rack.

Reference:
InstanceType
BuildInstance
ApiMemory

I hope this helps.

-Nick