Pulling Docker sandbox image fails because of corporate proxy & firewall rules

[nicolasbrechet]

Hi,

This project looks interesting but I'm blocked from using it because in my company, we don't pull images directly from the internet, but rather pull from our internal Artifactory instance.

I think it would be very useful to be able to define the source of the Docker sandbox image.

For example, instead of pulling ghcr.io/obot-platform/discobot:0.0.1-alpha57, I would be pulling from internal-artifactory.internal-domain/obot-platform/discobot:0.0.1-alpha57

Thanks !

[ibuildthecloud]

The other approach is to just bundle the image in the dmg. Would that work. I don't really need to pull it from the internet. I just don't want to have to deal with that configuration and then of course some will then want authentication. Are you going to have issues hitting the app updater service? There's a json file that you have to access from discobot.ai and then the app will download the new resoures from github releases.

[nicolasbrechet]

Bundling would indeed work.
And I think if the updater service properly use the system proxy, it should work as well.

[ibuildthecloud]

This should be fixed in the latest releases, but I haven't really tested that the update service will go through a proxy. I know for sure we're not setting up any proxy information inside of the agent sandboxes.