Github messages for voidlinux
 help / color / mirror / Atom feed
From: dm17 <>
Subject: Re: New package: docker-cli-compose-2.2.3
Date: Fri, 11 Feb 2022 13:11:38 +0100	[thread overview]
Message-ID: <20220211121138.Yoe9UeGdR1EZXEI5uPavhsoqY3N2R0ZXL28-3L5ZQmk@z> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 1295 bytes --]

New comment by dm17 on void-packages repository

> > Looks like docker compose (aka compose v2) has compose v1 compatibility on Arch (by running the old "docker-compose"), but not on Void.
> If you look at this PR, it was closed by [bf7aa5b](, I decided to go with just updating the package and not creating a new one. We also have a wrapper.
> I'm also wondering how
> > `du -sh /usr/libexec/docker/cli-plugins/docker-compose` could return 8.6M on Void while `du -sh /usr/lib/docker/cli-plugins/docker-compose` could return 31M on Arch. That seems like more of a size difference than the wrapper/helper for backward compatibility could account.
> I am not sure how you measured this, I see 21MB on aarch64-musl and 13MB on x86_64. I think it's because of stripping, but I am not sure if the difference is this big and if arch doesn't strip go programs.
> EDIT: the size reported by ls is actually 25MB, du reports disk usage

Ah thanks du vs ls shows much less of a difference :)

> We also have a wrapper.

How is this evoked? ```docker-compose disable-v2``` doesn't seem to work.

  parent reply	other threads:[~2022-02-11 12:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-02 22:26 [PR PATCH] docker-compose: update to 2.2.3 paper42
2022-02-04 22:01 ` [PR PATCH] [Updated] " paper42
2022-02-04 22:47 ` paper42
2022-02-05  1:01 ` New package: docker-cli-compose-2.2.3 paper42
2022-02-10 15:14 ` [PR PATCH] [Closed]: " paper42
2022-02-11  1:57 ` dm17
2022-02-11 11:54 ` paper42
2022-02-11 11:58 ` paper42
2022-02-11 12:11 ` dm17 [this message]
2022-02-11 13:15 ` paper42
2022-02-11 13:57 ` dm17

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220211121138.Yoe9UeGdR1EZXEI5uPavhsoqY3N2R0ZXL28-3L5ZQmk@z \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).