PyCharm Docker Compose Profiles: Do Unactivated Services Build Without `--no-build`?

Goal

Determine whether services that are defined with a profiles: key in a Compose file are built when launched from PyCharm, even if those profiles are not activated via the --profile flag or the COMPOSE_PROFILES environment variable.

Constraints & Uncertainty

PyCharm’s Docker Compose integration does not expose the --no-build option directly in its UI. The Compose spec states that services not matched by an active profile should not start, but it does not clarify whether the image build step is skipped automatically.

Specific Questions

• When a Docker Compose configuration is started from PyCharm, are services with inactive profiles still built?
• Does PyCharm provide a setting or flag to suppress building of services that are not part of an active profile?
• If not, can the Compose file or PyCharm’s run configuration be adjusted to implicitly use --no-build for such services?