All RUN commands were joined in order to minimize the layers size.

[dgroup]

During docker image building procedure you may observe warning
[WARNING]: Empty continuation line found.

It happens due to comments between multiple commands in the RUN statement.
The fix is quite simple - remove the comments.
From my points of view these comments are useful, thus I kept them as is.

That's a docker bug, nothing critical just a warning, see more details here - moby/moby#35004.

Could you, please, add me as a contributor?
Email: dgroup@ex.ua

[0crat]

@yegor256 please, pay attention to this pull request

[0crat]

Job gh:yegor256/threecopies#14 is in scope.

[yegor256]

@dgroup feel free to create "Contributors" section in README, if you want to be there, just like it's done here, for example: https://github.com/yegor256/cactoos#contributors

[yegor256]

@dgroup on a second thought it looks like an abuse of Docker file structure. We definitely should group commands, but not all commands in one RUN. Let's have groups.

[0crat]

@yegor256/z everybody who has role DEV are banned at this job; I won't be able to assign anyone automatically; consider assigning someone manually or invite more people to the project, as explained in §51

[0crat]

@yegor256/z everybody who has role DEV are banned at this job; I won't be able to assign anyone automatically; consider assigning someone manually or invite more people to the project, as explained in §51

[yegor256]

@dgroup are you planning to finish this?

[0crat]

@yegor256/z everybody who has role DEV are banned at this job; I won't be able to assign anyone automatically; consider assigning someone manually or invite more people to the project, as explained in §51

[0crat]

@yegor256/z everybody who has role DEV are banned at this job; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

[0crat]

@yegor256/z everybody who has role DEV are banned at this job; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

[yegor256]

@rultor out

[yegor256]

@0crat out

[0crat]

@0crat out (here)

@yegor256 The job #14 is now out of scope

[rultor]

@rultor out

@yegor256 I'm sorry, I don't understand you :( Check this page and try again please

[yegor256]

@0crat out

[0crat]

@0crat out (here)

@yegor256 The job is not in WBS, won't close the order

[dgroup]

Hi @yegor256
The changes were done within this pull request.

[dgroup]

@yegor256 reminder.

[0crat]

Job gh:yegor256/threecopies#14 is not assigned, can't get performer

[0crat]

This job is not in scope