shy-advantage-49800
12/01/2021, 7:54 PM./pants run src/docker/Dockerfile
?curved-television-6568
12/01/2021, 7:56 PMshy-advantage-49800
12/01/2021, 7:58 PMcurved-television-6568
12/01/2021, 8:19 PMcurved-television-6568
12/01/2021, 8:21 PMcurved-television-6568
12/01/2021, 8:26 PMambitious-actor-36781
12/02/2021, 12:26 AMProcfile
or docker-compose
system
with the latter, something like ./pants docker-compose up
would determine the container dependencies, build the containers, then generate a docker-compose file and docker-compose up
it.
Then (theoretically) when something changes, rebuilds and restarts the container.
Ultimately, why reinvent the wheel?curved-television-6568
12/02/2021, 8:11 AMdocker-compose
to setup an entire dev/test env locally, for instance.curved-television-6568
12/02/2021, 8:11 AMrun
too, though..eager-dress-66405
12/02/2021, 2:08 PM./pants run $target -- $docker_run_flags
curved-television-6568
12/02/2021, 3:19 PM$docker_run_flags
are passed to your image entrypoint..eager-dress-66405
12/02/2021, 3:26 PM--
? Flag after the run goal? Neither option "clean"curved-television-6568
12/02/2021, 3:43 PM./pants run --args="-p 80 --name foo ā¦" $target ā¦
?ambitious-actor-36781
12/02/2021, 9:10 PM--docker-args
would be consistent with other subsystems. e.g. --pytest-args
ambitious-actor-36781
12/02/2021, 9:11 PMdocker [global-opts] run [run-opts]
you'd actually need to separate the two.curved-television-6568
12/03/2021, 7:27 AMshy-advantage-49800
12/04/2021, 11:47 AMcurved-television-6568
12/04/2021, 11:51 AMshy-advantage-49800
12/04/2021, 11:54 AMshy-advantage-49800
12/04/2021, 12:02 PMcurved-television-6568
12/04/2021, 12:57 PM