Tensorflow Win Docker image
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 311
- Forks
- 139
- Avg merge
- 1h 28m
- Merged PRs (30d)
- 1
Description
Can we publish a small Wine+Tensorflow docker image in our Dockerhub account?
It could really help to make minor local Win debug activities instead of waiting for Kokoro label maintainers permission and slow CI building cycles, specially for python only bugs.
E.g. Follow my recent triage case at https://github.com/tensorflow/tensorflow/issues/48086#issuecomment-808227155
P.s. I know that Tensorflow still doesn't run in the source tree and so we need some bad hack to patch/edit installed python wheel files diractly. But it is better then nothing and to "bruteforce" the CI.
/cc @theadactyl @joanafilipa @mihaimaruseac
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the repository’s Docker and Docker Hub/Kokoro publishing entry points, then review how images are built and released. Confirm the required Wine and TensorFlow wheel setup and define a minimal Windows-debug image; done means it is published to the TensorFlow Docker Hub account and usable for the stated local Python-debug workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python, tensorflow
- Domain
- build-system, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100