To stay within your own conventions and help sorting, rename gradle tasks:
docker -> dockerBuild
generateDockerCompose -> dockerComposeGenerate
Clarify descriptions for those learning docker mostly via this tool:
//dockerBuild - build image in Docker from DockerFile (one single image operation is functioning)
//dockerRun- run a (built) Image in Docker (one single image operation is functioning)
//dockerComposeGenerate - generate docker compose yml file from palantir specific template file and stated (Version) dependancy information (one single compose operation is functioning and it cannot use a palantir Dockerfile template)
Also haven't figured out how to automatically rename the generated docker files, but still learning. [EDIT], doesn't look like you can... everything seems designed minimally, for a specific project application only and not for a flexible docker build automation and integration with other build plugins like kotlin multiplatform.
To stay within your own conventions and help sorting, rename gradle tasks: docker -> dockerBuild generateDockerCompose -> dockerComposeGenerate
Clarify descriptions for those learning docker mostly via this tool: //dockerBuild - build image in Docker from DockerFile (one single image operation is functioning) //dockerRun- run a (built) Image in Docker (one single image operation is functioning) //dockerComposeGenerate - generate docker compose yml file from palantir specific template file and stated (Version) dependancy information (one single compose operation is functioning and it cannot use a palantir Dockerfile template)
Also haven't figured out how to automatically rename the generated docker files, but still learning. [EDIT], doesn't look like you can... everything seems designed minimally, for a specific project application only and not for a flexible docker build automation and integration with other build plugins like kotlin multiplatform.