github-starred/flowsint
2
0
Fork 0
mirror of https://github.com/reconurge/flowsint.git synced 2026-05-07 04:09:49 -05:00
Code Issues 264 Packages Projects Releases 11 Wiki Activity

[GH-ISSUE #118] make dev Error #88

New Issue
Open
opened 2026-04-11 08:42:14 -05:00 by GiteaMirror · 9 comments
GiteaMirror commented 2026-04-11 08:42:14 -05:00
Owner
Copy Link

Originally created by @seklure on GitHub (Feb 6, 2026).
Original GitHub issue: https://github.com/reconurge/flowsint/issues/118

Ubuntu 22.04 Kernel 6.1.10
Use make dev command , The error message is as follows:

Starting DEV environment...
make check-env
make[1]: Entering directory '/data/flowsint'
Checking .env files...
make[1]: Leaving directory '/data/flowsint'
make build-dev
make[1]: Entering directory '/data/flowsint'
Building DEV images...
docker compose -f docker-compose.dev.yml build
unknown shorthand flag: 'f' in -f

Usage: docker [OPTIONS] COMMAND [ARG...]

Run 'docker --help' for more information
make[1]: *** [Makefile:48: build-dev] Error 125
make[1]: Leaving directory '/data/flowsint'
make: *** [Makefile:41: dev] Error 2

Originally created by @seklure on GitHub (Feb 6, 2026). Original GitHub issue: https://github.com/reconurge/flowsint/issues/118 Ubuntu 22.04 Kernel 6.1.10 Use make dev command , The error message is as follows: Starting DEV environment... make check-env make[1]: Entering directory '/data/flowsint' Checking .env files... make[1]: Leaving directory '/data/flowsint' make build-dev make[1]: Entering directory '/data/flowsint' Building DEV images... docker compose -f docker-compose.dev.yml build unknown shorthand flag: 'f' in -f Usage: docker [OPTIONS] COMMAND [ARG...] Run 'docker --help' for more information make[1]: *** [Makefile:48: build-dev] Error 125 make[1]: Leaving directory '/data/flowsint' make: *** [Makefile:41: dev] Error 2
GiteaMirror commented 2026-04-11 08:42:14 -05:00
Author
Owner
Copy Link

@dextmorgn commented on GitHub (Feb 6, 2026):

Hey @Alexro0t,

We are using docker compose v2 to run containers; it seems you might still be using docker compose v1.

Could you check:

docker version

and

docker compose version

If you don't see something like :

> docker compose version
# Docker Compose version v2.x.x

You are probably out of date. I would suggest to install latest version of docker and docker compose and restart :)

Let me know here if this fixed the problem.

<!-- gh-comment-id:3858838126 --> @dextmorgn commented on GitHub (Feb 6, 2026): Hey @Alexro0t, We are using docker compose v2 to run containers; it seems you might still be using docker compose v1. Could you check: ```bash docker version ``` and ```bash docker compose version ``` If you don't see something like : ```bash > docker compose version # Docker Compose version v2.x.x ``` You are probably out of date. I would suggest to install latest version of docker and docker compose and restart :) Let me know here if this fixed the problem.
GiteaMirror commented 2026-04-11 08:42:15 -05:00
Author
Owner
Copy Link

@seklure commented on GitHub (Feb 6, 2026):

Hey @Alexro0t,

We are using docker compose v2 to run containers; it seems you might still be using docker compose v1.

Could you check:

docker version
and

docker compose version
If you don't see something like :

docker compose version

Docker Compose version v2.x.x

You are probably out of date. I would suggest to install latest version of docker and docker compose and restart :)

Let me know here if this fixed the problem.

This is my docker env.

docker version
Client:
Version: 28.3.1
API version: 1.51
Go version: go1.24.4
Git commit: 38b7060
Built: Wed Jul 2 20:55:19 2025
OS/Arch: linux/amd64
Context: default

Server: Docker Engine - Community
Engine:
Version: 28.3.1
API version: 1.51 (minimum version 1.24)
Go version: go1.24.4
Git commit: 5beb93d
Built: Wed Jul 2 20:56:35 2025
OS/Arch: linux/amd64
Experimental: true
containerd:
Version: v1.7.27
GitCommit: 05044ec0a9a75232cad458027ca83437aae3f4da
runc:
Version: 1.3.3-0ubuntu1~22.04.3
GitCommit:
docker-init:
Version: 0.19.0
GitCommit: de40ad0

docker-compose version
Docker Compose version v5.0.2

<!-- gh-comment-id:3858859197 --> @seklure commented on GitHub (Feb 6, 2026): > Hey [@Alexro0t](https://github.com/Alexro0t), > > We are using docker compose v2 to run containers; it seems you might still be using docker compose v1. > > Could you check: > > docker version > and > > docker compose version > If you don't see something like : > > > docker compose version > # Docker Compose version v2.x.x > You are probably out of date. I would suggest to install latest version of docker and docker compose and restart :) > > Let me know here if this fixed the problem. This is my docker env. docker version Client: Version: 28.3.1 API version: 1.51 Go version: go1.24.4 Git commit: 38b7060 Built: Wed Jul 2 20:55:19 2025 OS/Arch: linux/amd64 Context: default Server: Docker Engine - Community Engine: Version: 28.3.1 API version: 1.51 (minimum version 1.24) Go version: go1.24.4 Git commit: 5beb93d Built: Wed Jul 2 20:56:35 2025 OS/Arch: linux/amd64 Experimental: true containerd: Version: v1.7.27 GitCommit: 05044ec0a9a75232cad458027ca83437aae3f4da runc: Version: 1.3.3-0ubuntu1~22.04.3 GitCommit: docker-init: Version: 0.19.0 GitCommit: de40ad0 docker-compose version Docker Compose version v5.0.2
GiteaMirror commented 2026-04-11 08:42:15 -05:00
Author
Owner
Copy Link

@dextmorgn commented on GitHub (Feb 6, 2026):

Can you output this (without the dash):

docker compose version
<!-- gh-comment-id:3859467057 --> @dextmorgn commented on GitHub (Feb 6, 2026): Can you output this (without the dash): ``` docker compose version ```
GiteaMirror commented 2026-04-11 08:42:16 -05:00
Author
Owner
Copy Link

@seklure commented on GitHub (Feb 10, 2026):

Can you output this (without the dash):

docker compose version
Image
<!-- gh-comment-id:3874584023 --> @seklure commented on GitHub (Feb 10, 2026): > Can you output this (without the dash): > > ``` > docker compose version > ``` <img width="435" height="90" alt="Image" src="https://github.com/user-attachments/assets/37e7f585-8d73-4265-965e-8c3d6d613213" />
GiteaMirror commented 2026-04-11 08:42:16 -05:00
Author
Owner
Copy Link

@dextmorgn commented on GitHub (Feb 10, 2026):

Yes so you probably are using an older version of docker compose, as the new version command moved from:

docker-compose

to

docker compose

While docker-compose synthax is still supported, I still want to enforce using docker compose as a witness to using a later version.

Two options for you:

  • either update your docker setup to docker compose v2 using the official install
  • Change occurrences of docker compose with docker-compose in the Makefile. Hopefully this would work with your setup without too much side effects

Let me know how this worked for you !

<!-- gh-comment-id:3876145157 --> @dextmorgn commented on GitHub (Feb 10, 2026): Yes so you probably are using an older version of docker compose, as the new version command moved from: ```bash docker-compose ``` to ```bash docker compose ``` While `docker-compose` synthax is still supported, I still want to enforce using `docker compose` as a witness to using a later version. Two options for you: - either update your docker setup to docker compose v2 [using the official install](https://docs.docker.com/compose/install/) - Change occurrences of `docker compose` with `docker-compose` in the Makefile. Hopefully this would work with your setup without too much side effects Let me know how this worked for you !
GiteaMirror commented 2026-04-11 08:42:16 -05:00
Author
Owner
Copy Link

@seklure commented on GitHub (Feb 10, 2026):

Yes so you probably are using an older version of docker compose, as the new version command moved from:

docker-compose
to

docker compose
While docker-compose synthax is still supported, I still want to enforce using docker compose as a witness to using a later version.

Two options for you:

  • either update your docker setup to docker compose v2 using the official install
  • Change occurrences of docker compose with docker-compose in the Makefile. Hopefully this would work with your setup without too much side effects

Let me know how this worked for you !

Did you mean that installing Docker Compose v2 is the way recommended by the official documentation, which involves installing it using the plugin method?
https://docs.docker.com/compose/install/linux/#install-the-plugin-manually

<!-- gh-comment-id:3876273334 --> @seklure commented on GitHub (Feb 10, 2026): > Yes so you probably are using an older version of docker compose, as the new version command moved from: > > docker-compose > to > > docker compose > While `docker-compose` synthax is still supported, I still want to enforce using `docker compose` as a witness to using a later version. > > Two options for you: > > * either update your docker setup to docker compose v2 [using the official install](https://docs.docker.com/compose/install/) > * Change occurrences of `docker compose` with `docker-compose` in the Makefile. Hopefully this would work with your setup without too much side effects > > Let me know how this worked for you ! Did you mean that installing Docker Compose v2 is the way recommended by the official documentation, which involves installing it using the plugin method? https://docs.docker.com/compose/install/linux/#install-the-plugin-manually
GiteaMirror commented 2026-04-11 08:42:16 -05:00
Author
Owner
Copy Link

@dextmorgn commented on GitHub (Feb 10, 2026):

No I meant basically installing the latest version of docker and docker compose, not the plugin.

I would suggest using chatgpt to obtain a step by step guide on how to update your Docker ≥ 20.10.

Let me know

<!-- gh-comment-id:3876519684 --> @dextmorgn commented on GitHub (Feb 10, 2026): No I meant basically installing the latest version of docker and docker compose, not the plugin. I would suggest using chatgpt to obtain a step by step guide on how to update your Docker ≥ 20.10. Let me know
GiteaMirror commented 2026-04-11 08:42:17 -05:00
Author
Owner
Copy Link

@seklure commented on GitHub (Feb 11, 2026):

No I meant basically installing the latest version of docker and docker compose, not the plugin.

I would suggest using chatgpt to obtain a step by step guide on how to update your Docker ≥ 20.10.

Let me know

According to the official documentation, the one being used is docker-compose rather than docker componse.

<!-- gh-comment-id:3884820372 --> @seklure commented on GitHub (Feb 11, 2026): > No I meant basically installing the latest version of docker and docker compose, not the plugin. > > I would suggest using chatgpt to obtain a step by step guide on how to update your Docker ≥ 20.10. > > Let me know According to the official documentation, the one being used is docker-compose rather than docker componse.
GiteaMirror commented 2026-04-11 08:42:17 -05:00
Author
Owner
Copy Link

@dextmorgn commented on GitHub (Apr 10, 2026):

Hi @seklure, have you been able to manage your setup issue ?

<!-- gh-comment-id:4226614519 --> @dextmorgn commented on GitHub (Apr 10, 2026): Hi @seklure, have you been able to manage your setup issue ?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
documentation
enhancement
pull-request
Mirrored from GitHub Pull Request
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/flowsint#88
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?