Debugging configure/make/install

During the configure phase, the configure script is complaining, and suggests that I look in config.log. Is there anyway to view config.log?
The old containers seem to be still running, but I did no let this deter me from inspecting the device, as I have noticed that old containers seem to persist until a reboot.
Anyway, when I log into host_os, I cannot find config.log.

[main]     checking whether the C compiler works... 
[main]     no
[main]     configure: error: in `/usr/src/app':
[main]     configure: error: C compiler cannot create executables
[main]     See `config.log' for more details
[main]     Removing intermediate container b68768d66c96

Perhaps you could try building the container locally using balena-cli (balena build ...). This will allow you to debug this issue by inspecting generated image layers locally, or just temporarily adding .. (./configure || true) && cat < config.log to the RUN command in your Dockerfile.

Thanks for the info.
I am attempting your first suggestion. So, I ssh’d into the device

balena ssh 00c1c92.local

Now I am logged in, and I try to clone my repo, but I don’t have git installed.
Should I create a new host_os or container that has the tools installed?
Am I on the right track?
To answer my own question: Creating a container with all the tools installed worked perfectly, and I am now able replicate the configure failure, and read the config.log, which was my orginal question.
Not sure if this is the best approach, but it seems to be working.
Thanks for the help.

I think Anton’s original thought was to have the balena CLI installed on your local laptop or PC, and use it to build the container right there on your machine (as opposed to the cloud builders). However, your method will give you the same results, so, that works too!