so cannot work

i guess we could support writing an html page

ok, found the issue.

enable_deck=True

on the

ContainerTask

works just fine, but Flyte does not seem to forward this arg / state to the container (kinda makes sense!) and thus in-container Deck logging fails here: https://github.com/flyteorg/flytekit/blob/b6f806d2fa493eb78f9c2d964989b5a5a94a44ed/flytekit/deck/deck.py#L92 notably, inside the container,

FlyteContextManager.current_context()

also gets no execution state and such. My guess is that

ContainerTask

is not really designed to forward in params like deck and such, so maybe just a

log.warning()

in the

ContainerTask

ctor or something like that, to notify the user that Decks won't work, would be big halp. For my own use case, we were trying to use

Deck

as an interim workaround while setting up other logging, so am likely not to have continuing interest in a Decks-on-ContainerTask feature. Decks did work great for normal `task`s tho!