Improve Dockerfile

[trottomv]

• Use VIRTUAL_ENV into Dockerfile instead of user system path
• Improve local image size optimization
• Remove k8s and add terraform directory from .dockerignore

[niccolomineo]

I would do without depending on customizing the $PATH in the IDE, as this PR is currently hinting at. Else, we would make the development environment unreasonably stiffer for all non Talos-based projects.

[trottomv]

I would do without depending on customizing the $PATH in the IDE, as this PR is currently hinting at. Else, we would make the development environment unreasonably stiffer for all non Talos-based projects.

The IDE $PATH isn't something that can be managed directly from the Dockerfile. However, I imagine that if these changes are introduced to an existing and ongoing project, it might simply require adjusting the Python interpreter path in the IDE settings.

[niccolomineo]

I would do without depending on customizing the $PATH in the IDE, as this PR is currently hinting at. Else, we would make the development environment unreasonably stiffer for all non Talos-based projects.

The IDE $PATH isn't something that can be managed directly from the Dockerfile. However, I imagine that if these changes are introduced to an existing and ongoing project, it might simply require adjusting the Python interpreter path in the IDE settings.

As I mentioned already, I'd rather not do that, because unfortunately 20tab does not entail Talos-based projects only.

[trottomv]

As I mentioned already, I'd rather not do that, because unfortunately 20tab does not entail Talos-based projects only.

I understand your concern about the broader impact on non-Talos projects. However, this PR is specifically focused on Talos, so the adjustments discussed would apply only within this project's scope. This should prevent any unintended constraints on unrelated 20tab projects.

[niccolomineo]

As I mentioned already, I'd rather not do that, because unfortunately 20tab does not entail Talos-based projects only.

I understand your concern about the broader impact on non-Talos projects. However, this PR is specifically focused on Talos, so the adjustments discussed would apply only within this project's scope. This should prevent any unintended constraints on unrelated 20tab projects.

What's with the ChatGPT-style of reply? 😄

Anyways, anything ending up in Talos should make the team's life easier. That's the angle we should keep in mind.