Update default Dockerfile Pycytominer branch from master to main

[d33bs]

Pycytominer now uses main instead of master as the default branch. This updates the Dockerfile here to be in alignment.

Thanks in advance for any thoughts and suggestions you may have here! Please don't hesitate to let me know if you have any questions.

[gwaybio]

LGTM

Do we have to bump pycytominer version?

[d33bs]

Thanks @gwaybio ! The Dockerfile will grab the latest updates from source under the main branch currently. I deferred to keep the functionality here the same for now in case it makes a difference with concerns to CellProfiler usecases. When the time is right, a new image could be pushed to Docker Hub with the 1.0.x tag for general availability. We might want to make sure anything which references the "latest" tag is ready to receive the updates from Pycytominer 1.0.x.

Asides:

• I wonder if it'd be beneficial to add a "release-based" Dockerfile and/or image here or in the Pycytominer repo (adding to the existing deployments on PyPI and Conda-forge).
• We may also want to incorporate the cell-locations extra here at some point.

[bethac07]

I wonder if it'd be beneficial to add a "release-based" Dockerfile and/or image here or in the Pycytominer repo (adding to the existing deployments on PyPI and Conda-forge).
We may also want to incorporate the cell-locations extra here at some point.

All of that is fine with me! We can also do commit based tags, since the version just passed through is git checkout $version . This was definitely not the MOST one could do, it was just a minimal version so we could do this. But I am all for more functionality and more efficient/lazier builds.

[d33bs]

Thanks @bethac07 ! I'll create a pair of issues to track this here and in the Pycytominer repository.