Code Monkey home page Code Monkey logo

Comments (7)

feiskyer avatar feiskyer commented on July 17, 2024

cc @PatrickLang @adelina-t

from busybox.

tianon avatar tianon commented on July 17, 2024

As I noted in kubernetes/kubernetes#61097, this requires upstream support for Windows which does not currently exist. There are a couple discussions on their mailing list (I found a few interesting ones by searching for site:busybox.net combined with "Windows", "win32", and "mingw"), and I also went as far as trying to compile against MinGW without much success.

Barring actual upstream support for this, I'm sorry but there's not much we can do. From what I can see, upstream needs some patching and also a champion to maintain support going forward.

If someone can demonstrate building unpatched sources from busybox.net for Windows, I would be thrilled to revisit this.

from busybox.

dims avatar dims commented on July 17, 2024

@tianon when you say upstream which repository do you mean? is there a issue tracker there?

from busybox.

feiskyer avatar feiskyer commented on July 17, 2024

this requires upstream support for Windows which does not currently exist

@tianon I thought upstream means docker-library/busybox. Do you mean the code base of busybox itself?

from busybox.

tianon avatar tianon commented on July 17, 2024

from busybox.

PatrickLang avatar PatrickLang commented on July 17, 2024

I don't know the full history here, but there is a fork of busybox that's tailored to mingw at https://github.com/rmyorston/busybox-w32 . If that project accepts a Dockerfile and were to publish an image - would it be acceptable to use that version?

from busybox.

tianon avatar tianon commented on July 17, 2024

Not for the busybox "official image" -- it isn't exactly fair to the BusyBox project if we use an unofficial port and call it more than that, so I wouldn't be entirely comfortable with that route (and we've had poor experiences with doing/allowing that in the past; see the redis Windows variants for an example of that where the fork was never really on par with upstream and eventually died entirely).

On the flip side, it should be pretty trivial for someone else to take that, build it, publish an image, and combine that image together with the image we publish (in some automated fashion, probably) under a single manifest list.

I would really hope the ultimate goal of that project would be to get merged back into the BusyBox tree proper. 😅

from busybox.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.