feat(build): detect if the current environment is running before building

[kemingy]

Description

Currently, the logic is: build -> check if the same container is running -> remind the user to use --force or manually clean it.

We should make it to: detect the current environment -> remind the user if it's running -> build

---

Message from the maintainers:

Love this enhancement proposal? Give it a 👍. We prioritise the proposals with the most 👍.

[Belyenochi]

If no one else, please assign it to me :-).

[kemingy]

If no one else, please assign it to me :-).

/assign @Belyenochi

[gaocegege]

Thanks!

And, ask us if there is any question about this feature.

Here is the discord invitation link: https://discord.gg/KqswhpVgdU

[gaocegege]

Hi @Belyenochi

Are you still working on the issue?

[Belyenochi]

Hi @Belyenochi

Are you still working on the issue?

Sorry for not updating this issue, I will try to submit the PR this week.

[Belyenochi]

@gaocegege , hi gaocegege, I have two not so sure about the implementation of this problem

1. Whether the original mirroring logic of rebuilding the image through --force needs to be retained, I understand that it may be necessary
2. When reminding the user that the same container is running, whether the user needs to use a judgment like yes or no to allow or block the build or is it just a reminder and the default result is the same as the original --force logic

[gaocegege]

@kemingy Could you please help answer the questions?

[kemingy]

1. Whether the original mirroring logic of rebuilding the image through --force needs to be retained, I understand that it may be necessary

Yes. We should keep the --force.

2. When reminding the user that the same container is running, whether the user needs to use a judgment like yes or no to allow or block the build or is it just a reminder and the default result is the same as the original --force logic

I think a reminder should be easy to implement.

[Belyenochi]

1. Whether the original mirroring logic of rebuilding the image through --force needs to be retained, I understand that it may be necessary

Yes. We should keep the --force.

2. When reminding the user that the same container is running, whether the user needs to use a judgment like yes or no to allow or block the build or is it just a reminder and the default result is the same as the original --force logic

I think a reminder should be easy to implement.

thanks @kemingy @gaocegege :-).