compose support?

[magnusviri]

Will you be creating a tool that allows users to use docker_compose.yml files?

See https://docs.docker.com/compose/.

[awilfox]

Yes, I would also love to see Compose support for container. Is this something that would accepted as a contribution?

[ttys3]

just found a impl https://github.com/mcrich23/container-compose

[bergrahm]

I am a heavy-weight compose user. Having the option to drop and replace would dramatically increase the chance for me to adopt this tool without hassle. Great work by the way!

[codedoga]

+1

[psy0rz]

Without compose support i will just keep using docker desktop for now. What would be the advantage of this new system?

[ArquitetoMovel]

I'm using the https://orbstack.dev it also is made in swift and not use vm

[66Ton99]

https://orbstack.dev/ uses VM underhood

[koi-tattoo]

I've rolled up a script to emulate some functionalities of docker-compose https://gist.github.com/koi-tattoo/1decd7f52f55ddb902e8a9eb78f8c587.
I mostly generated it through claude 4 sonnet as I was just trying to have something working fast. It managed to up this compose file https://gist.github.com/koi-tattoo/5f91de153768865d6d29f3773564a75d decently, maybe you guys can try to use it to easily test apple containers through your already established compose files.

Edit: see the issue docker/compose/issues/12934, maybe it is on docker-compose's end to implement this feature.

[ralfkrause]

I’ll test it and will give an update here.

[ralfkrause]

The scripts does the main things.
During up volumes if not defined with type bind are skipped. Giving error message 'named volumes...'.
During down I got the error message that the container could not be deleted. But that's just because they are getting started with option --rm. But that's no big deal.
Setting the hostname of the container is not supported. But that's because it's not supported by Apples container system. At least not at the moment.
It's the same as the container name.
Traffic between container of the same multi container project does not work when using the hostname of the container. But there is no problem when using the IP address.

But far from that all I tested works.

[t3chn0m4g3]

yes, compose is the peanut-butter and jelly!

[psy0rz]

Dont get me wrong its super cool apple does this!

[bgottsch]

+1

some integration pointers:

• naming: container compose?
• load balancers like Traefik as a container

[llmons]

+1

[pszymkowiak]

+1

[dmatton]

+1

[koi-tattoo]

According to docker/compose#12934, it could be done if the apple container runtime supports the Moby API (https://github.com/moby/moby/blob/master/api/README.md)

[mani-arjunan]

+1

[tarikweiss]

+1

[EugeneBad]

+1E6

[iperezx]

+1M

[arch-fan]

i'll make a somersault if this becomes real

[marque-antoine]

+1

[manuelsucco]

+1

[iMUngHee]

+1

[empireshades]

+5M plzzzzz. 🙏

[meccin]

+1

[APKiwi]

+1

[vxnkjyffmq-code]

+1

[Jeremymr2]

+1

[g-battaglia]

+1

[arch-fan]

Sad #239 (comment)

[Mcrich23]

To everyone here that is new and adding +1, please stop. I don't know about others, but I get every single one of those emails. The Apple Container team knows it is desired and has tabled discussions for a first party solution for now (see #239 (comment)). If you would like a solution right now, Socktainer, Container-Compose, and @mazdak's fork with compose are all great options.

Personally, I will likely continue to use Container-Compose since it is available with just brew install container-compose, but to each their own. I would like to express immense gratitude to everyone who has pushed for this to happen and I am sad to see this conversation being tabled indefinitely without strong plugin support (see #630, #717, and #633).

I hope something 1st party will come soon, but I honestly have no clue.

Happy Building!
— Morris

[luisneto]

@Mcrich23 : In my opinion, we should avoid creating a new discussion. It would make it more confusing.

Project maintainers can delete or hide comments, marking them as spam, off-topic and other reasons. (Link)

[luisneto]

Actually, comments in discussions can't be hidden but they can be deleted: Moderating discussions - GitHub Docs.

@jglogan: tagging you here to bring your attention to this.

[Mcrich23]

Regardless, this discussion revolves around asking for compose support and the other would be a fresh start where I can manage a FAQ and we can have healthy productive conversation on future implementation. I won't do it if people are not interested, but I would be happy to if there is interest in a proper discussion.

[jglogan]

@Mcrich23 "compose support?" as it is, seems like the right place for anyone to come and talk about compose support today, add +1s, and yeah, vent some frustration that there's not compose directly in container or some other apple/container-* repo.

You and anyone else can create additional discussions to talk about compose development or development for any other feature. IMO what you're specifically proposing seems like a good idea - maybe include a link at the top to redirect the general "why isn't there compose?" posts here.

[stivens]

As I said. Your request does not work 😆

[jglogan]

without strong plugin support (see #630, #717, and #633)

@Mcrich23 #633 and #717 relate to passing an OptionGroup value (or any property) from a your code (possibly from a OptionGroup-valued property on a ParseableCommand you define, but it could come from anywhere) to a corresponding property value on a ParseableCommand in ContainerCommands, right?

Can you point me at code in your project where this is impacting you? Or is it the case that there are commands that you're just not choosing to implement because this capability isn't there?

[Mcrich23]

Sounds good. My usage is currently limited to logging, but that was not always the case. I can see this being used in regards to settings such as process, resource, and dns. These are things developers may not consider but some users will care about.

I agree with you, creating a system that uses macros lightens the load towards supporting plugins for both upstream maintainers and developers, since all that is required to update passthrough is recompilation with the new version because the function updates automatically.

[jglogan]

I'm not convinced that macros are the answer here but my mind is open. As the CLI is more stable now, it may make more sense to revive your original PR and make all of the properties part of the public API. That one was always more of a "not yet" than a full on "no".

[Mcrich23]

Sounds good. Although I will caution that initializing a ParseableCommand struct requires setting every property before calling it or argument-parser will fatal error. I am wondering if we keep initializers internal to force something like the current API but where specific properties can be set afterwards.

var foo = Bar.parse(["baz"])
foo.logging = self.logging

[jglogan]

Do you want to start a discussion topic specifically for the challenges you've encountered integrating your app with container via ContainerCommands? A general topic for compose implementors seems useful but this issue, while related, seems to be distinct from that.

[Mcrich23]

Sounds good. I have created that discussion here.

[LixFerox]

+1

[lowrey2142]

+1