Network issues that prevent charms from being insalled don't reflect in charm state

This is normally a result of a proxy blocking the docker engine from pulling container images. Ideally, if an image can't be pulled, the charm should enter a failed state

Start by reproducing a charm installation while a proxy prevents the Docker engine from pulling an image, then trace how that failure is reported to the charm state. Done means the installation failure is represented by a failed charm state, with coverage for the blocked image-pull scenario.

Written by the indexing model from the issue text.