Docker container with MacPorts

Karan Sheth karan.sheth at
Mon Jul 15 12:32:12 UTC 2019

OK sorry, actually if we are just pushing Dockerfile with it's setup
documentation then I guess, there's no need of another repo.

So it could be something like
- Dockerfile and it's documentation
- Azure CI to test run if the dockerfile works perfectly
- Moving forward as you said we can add official Macports Image to docker
registry so that can also be automated via CI

Sounds good?

Karan Sheth

On Mon, Jul 15, 2019 at 1:08 PM Karan Sheth <karan.sheth at> wrote:

> Hey,
> Ok great. I will write a basic guide by tonight.
> Just tell me where should I push the code.
> I would prefer if it is a different repository atleast for now but I am
> fine with anything.
> Thanks,
> Karan Sheth
> On Mon, Jul 15, 2019 at 2:58 AM Mojca Miklavec <mojca at> wrote:
>> Dear Karan,
>> On Wed, 26 Jun 2019 at 16:00, Karan Sheth wrote:
>> >
>> >> My suggestion would be: could you perhaps share the sources
>> >> (Dockerfile I guess; together with some basic usage instructions)? We
>> >> could probably add a repository under github/macports-gsoc or so. Then
>> >> I could at least build an image locally instead of getting something
>> >> incompatible.
>> >
>> > I had previously just docker pulled ubuntu and installed macports
>> manually on it and then commiting the changes.
>> > I don't fully understand why the error occurred for you, isn't docker
>> supposed to be free of such errors?
>> > Please test the Dockerfile attached with this mail by building it using
>> "docker build".
>> > It might take upto 30 to 45min to build.
>> Can we push this hobby project that you made further and commit the
>> changes into one of the MacPorts repositories (including some super
>> basic documentation about how to run it) before it gets lost?
>> For the moment I would only commit the sources (configuration) since
>> the binary image is still causing some issues due to bugs in macports
>> base (which need to get fixed anyway).
>> I would either put the configuration somewhere in
>> or maybe macports-contrib, or its own repository altogether.
>> We could of course also make some official "MacPorts" images, but
>> that's the next stage.
>> And we could try to generate portindex for linux on our server, which
>> would dramatically reduce the build time. That said, I'm not even
>> entirely sure if building portindex should be part of the image
>> generation steps. The package index is definitely missing when you
>> fetch an ubuntu image, for example, for the sake of saving space.
>> Any thoughts?
>> Mojca


 <>        <>  
<>  <>  <>  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the macports-dev mailing list