Is it wrong to have multiple Docker images per app?

1

I have a crawler app that starts on demand. I create a new machine using the REST API, I specify the image I want, it does its work, it sends the data to another container, and it exits itself. I have two images; one for HTTP crawls, and one for browser-based crawls.

If I want to scale workers, I’d expect I’d have to build that into my design; it would not be a case of just making more machines per work item. So, for this app, I’d not use the Fly scaling feature; it would not make sense.

In the Machines page for this app, I see this warning:

Multiple image warning
Multiple image warning1216×159 37.9 KB

I can see why this is good advice in general, but do I need to be worried about it? I probably could split the app into two, but they feel conceptually like one app to me. Could this stop working?

2

this doesn’t work with fly deploy, but it’s fine to do that if you’re creating machines yourself. the dashboard is very targeted towards the fly deploy / PaaS workflow these days; I’d just ignore it and keep using Machines API.

3

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.