has anyone gotten `context.pdb.set_trace()` to wor...
# announcements
c
has anyone gotten
context.pdb.set_trace()
to work with docker-compose? i added
stdin_open: true
and
tty: true
to my docker-compose service but it still doesn't let me interact with the terminal
m
maybe try running the service in a separate command -- bring everything else up, then
docker-compose run
the specific service
i didn't even realize you could set
tty:true
in a docker compose file and would not be surprised if it worked in some unexpected way
c
hm
another question actually, then, is how do you use the
docker-compose run
command with dagster? when i try
docker-compose run dagit "dagster pipeline execute ..."
it complains that there is an extra unexpected argument
so i have to do
docker-compose run --entrypoint "dagster pipeline execute ..." dagit
i have a feeling that i shouldn't be replacing the entrypoint
but maybe i'm wrong
also, side question, is it possible to run
docker run ...
with a
.env
file? (not a dagster question, but since you're here 😛 )
cause part of the reason i'm using compose is for the
.env
file
m
hmm
replacing the entrypoint is probably the right thing if you're running a one-off command in any container
c
ok glad to hear that i'm not too far off then
m
i think you can pass
--env-file
to docker run
there was at least at one point a lot of back and forth in docker world about entrypoint vs cmd, and i'm really several years behind on that / have stopped being able to care, but i think the community settled on using entrypoint for this
c
oh hey, what do ya know! i should read `--help`s more often
haha same, i think i gave up on the
entrypoint
vs
cmd
argument as well