Vscode devcontainer

[bhack]

I know we closed #48679 but as Codespaces is GA now please keep this open so that in the meantime we have a PR where the user could test and bootstrap Github Codespaces and we could collect some feedback.

[bhack]

Keras has already merged its own keras-team/keras@4c9cf43

[bhack]

I don't know if Tensorflow team members have this setting enabled, if not it will be hard to test this in Codespaces for them (but It is still ok for Vsocde with remote extension):

https://docs.github.com/en/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization

[bhack]

/cc @yarri-oss

[bhack]

Just a small reminder.
Codespaces is in free trial until September 10, 2021 then we need to pay the VM instance to test this on the Github Codespace VM or with the Vscode browser.

Of course it will be still free to test on our your HW resources with Vscode desktop and the remote extension.

[bhack]

@angerson @mihaimaruseac I have minimized he Dockerfile and started to use your new manylinux2014 (currently gpu-only) images.

This new setup is oriented to a Docker rootless installation. See
microsoft/vscode-remote-release#4646
moby/moby#41497

[bhack]

@Chuxel Do you know why also using this the bazel cache is invalidated on every VSCode restart?

[bhack]

I've debugged a little more and it is seem to related code insider (daily) update restart. Let me know if you want an upstream ticket.

[bhack]

@Chuxel I've an upstream ticket now at microsoft/vscode-dev-containers#1453

[bhack]

@mihaimaruseac @angerson @yarri-oss You can test this clicking on the code button

[bhack]

Note: with the Codespace "free tier" available disk space (individual account) you will have a no space left on device cause with our manylinux/docker refactory effort we still have only a CUDA embedded image that is very large to run on the "free tier".
See more at tensorflow/build#47

[bamurtaugh]

Hi folks 👋! I wanted to provide some updates on development containers that might make this PR more interesting (cc @angerson as part of the initial PR thread).

Our team is working on an open dev container specification, so that any user in any tool can create and connect to dev containers. This includes tools beyond VS Code or Codespaces.

We recently released the reference implementation as an open source CLI, in addition to an initial version of the spec. We now have a devcontainers org for these repos and a site where you can read more about this effort: https://containers.dev/.

We also introduced a customizations property in which tool-specific properties live (additional info).

The CLI and spec are both in active development, so they'll continue to evolve, especially with external feedback. We'd love to hear if the spec helps make this PR more viable to become part of TensorFlow, and if there is any feedback or questions that'd make this a better fit - we're more than happy to discuss and collaborate. Thanks!

[bhack]

Thank you @bamurtaugh for your team updates I hope that @learning-to-play and @angerson could re-evaluate this.

In the meantime, on my side, one of the major blockers on this is the upstream issue we have at microsoft/vscode-remote-release#6746.

[gbaned]

@learning-to-play, @angerson, @bhack Any update on this PR? Please. Thank you!

[bhack]

@theadactyl Can we try to reply to @bamurtaugh?She is a Vscode PM at Microsoft

Thanks

[bhack]

@bamurtaugh Any new on Vscode side for microsoft/vscode-remote-release#6746?

[bamurtaugh]

Thanks for the ping @bhack!

Our team has been actively focused on specification work and an updated plan for community contributions and the vscode-dev-containers repo moving forward, which we've now outlined in this issue: microsoft/vscode-dev-containers#1589. This includes moving to a couple new repos for images and Features (https://github.com/devcontainers/images, https://github.com/devcontainers/features), and we anticipate to have a similar repo and process for templates/definitions.

Please let me know if you have any questions, thank you!

[bhack]

@bamurtaugh For TF we need to find a solution for the VSCode ticket at microsoft/vscode-remote-release#6746

Do you have any update?

[bamurtaugh]

Apologies for a potential lack of clarity in my original comment. I meant to explain that our team's primary work has been on the dev container spec and the items I highlighted. microsoft/vscode-remote-release#6746 is on the backlog, but spec work has been at the forefront, so there are no new updates on microsoft/vscode-remote-release#6746 at this time.

[bhack]

@bamurtaugh Thanks for the clarification.

[bhack]

Just a side note for @tensorflow/sigbuild-dockerfile-editors.
Now the devcontainers could be tested with an official Github Action:
https://github.com/devcontainers/ci/blob/main/docs/github-action.md

[bhack]

Just a side note for @tensorflow/sigbuild-dockerfile-editors. Now the devcontainers could be tested with an official Github Action: https://github.com/devcontainers/ci/blob/main/docs/github-action.md

I've added this with a PR in Keras-cv keras-team/keras-cv#893

[gbaned]

Hi @bhack, @bamurtaugh, @angerson Any update on this PR? Please. Thank you!

[bhack]

Hi @bhack, @bamurtaugh, @angerson Any update on this PR? Please. Thank you!

Still waiting a solution from @bamurtaugh and the MS vscode remote team for microsoft/vscode-remote-release#6746

On the TF side I need to check if @MichaelHudgins is still interested in this work.

[gbaned]

Hi @bhack Any update on this PR? Please. Thank you!

[bhack]

Still waiting for that ticket

[gbaned]

Hi @bhack Any update on this PR? Please. Thank you!