Why generated image name so long? Can I specify the name for the generated image?

[Jianzhi Li (epic1219)]

The generated image's name is too long, nearly take half of my screen. And when I run docker ps -a, the table is a mess cause one container's information takes two rows.

[Samruddhi Khandale (samruddhikhandale)]

Hi 👋

Are you creating the container with the dev container CLI? If so, have you tried using the --image-name option to explicitly specify the image name?

[Mortiemi]

Yeah, that will do. Since you dropped the image name part. But I think image and container name should always be displayed.

[~]$ docker images -a --format 'table {{.Repository}}\t{{.Tag}}'

REPOSITORY                                                                      TAG

vsc-proj-3e60c91bdc1d909edd1fc361d8ecb0d31dd68062d6584622f55aa2423332e776-uid   latest

infra/db/mysql                                                                  8.0.36

debian                                                                          bookworm



[~]$ docker ps -a --format 'table {{.ID}}\t{{.Names}}\t{{.Image}}'

CONTAINER ID   NAMES               IMAGE

f5a0b785bc56   mysql8              infra/db/mysql:8.0.36

fb83dbb6dd63   charming_shockley   vsc-proj-3e60c91bdc1d909edd1fc361d8ecb0d31dd68062d6584622f55aa2423332e776-uid:latest

[Mortiemi]

Yeah, that will do. Since you dropped the image name part. But I think image and container name should always be displayed.

[~]$ docker images -a --format 'table {{.Repository}}\t{{.Tag}}'

REPOSITORY                                                                      TAG

vsc-proj-3e60c91bdc1d909edd1fc361d8ecb0d31dd68062d6584622f55aa2423332e776-uid   latest

infra/db/mysql                                                                  8.0.36

debian                                                                          bookworm



[~]$ docker ps -a --format 'table {{.ID}}\t{{.Names}}\t{{.Image}}'

CONTAINER ID   NAMES               IMAGE

f5a0b785bc56   mysql8              infra/db/mysql:8.0.36

fb83dbb6dd63   charming_shockley   vsc-proj-3e60c91bdc1d909edd1fc361d8ecb0d31dd68062d6584622f55aa2423332e776-uid:latest

[Galvan hernandez (zuriel5zurielg20)]

Yeah, that will do. Since you dropped the image name part. But I think image and container name should always be displayed.

[~]$ docker images -a --format 'table {{.Repository}}\t{{.Tag}}'
REPOSITORY                                                                      TAG
vsc-proj-3e60c91bdc1d909edd1fc361d8ecb0d31dd68062d6584622f55aa2423332e776-uid   latest
infra/db/mysql                                                                  8.0.36
debian                                                                          bookworm

[~]$ docker ps -a --format 'table {{.ID}}\t{{.Names}}\t{{.Image}}'
CONTAINER ID   NAMES               IMAGE
f5a0b785bc56   mysql8              infra/db/mysql:8.0.36
fb83dbb6dd63   charming_shockley   vsc-proj-3e60c91bdc1d909edd1fc361d8ecb0d31dd68062d6584622f55aa2423332e776-uid:latest

,)

[Mortiemi]

Yeah, that will do. Since you dropped the image name part. But I think image and container name should always be displayed.

[~]$ docker images -a --format 'table {{.Repository}}\t{{.Tag}}'

REPOSITORY                                                                      TAG

vsc-proj-3e60c91bdc1d909edd1fc361d8ecb0d31dd68062d6584622f55aa2423332e776-uid   latest

infra/db/mysql                                                                  8.0.36

debian                                                                          bookworm



[~]$ docker ps -a --format 'table {{.ID}}\t{{.Names}}\t{{.Image}}'

CONTAINER ID   NAMES               IMAGE

f5a0b785bc56   mysql8              infra/db/mysql:8.0.36

fb83dbb6dd63   charming_shockley   vsc-proj-3e60c91bdc1d909edd1fc361d8ecb0d31dd68062d6584622f55aa2423332e776-uid:latest

[mbcmbv91-ai]

Hi

[mbcmbv91-ai]

Hi

[Muhamad Sazwan Bin Ismail (Sazwan96)]

https://github.com/Sazwan96/SGAE-Data-Lake.git
The Sazwan96/SGAE-Data-Lake public repository serves as the architecture for the SISTEM MANAGEMENT ALL WEBSITE OPERATIONS. It contains 23 commits on the main branch.

Repository Files Overview

The repository functions as a centralized data lake containing core system documentation, sovereign AI reports, infrastructure frameworks, and official records, including:
• SGAE Core Systems: Essential project guides and system documents like SGAE 2.0 ULTIMATE v32.0 · MUHAMAD SAZWAN BIN ISMAIL · COMPLETE SYSTEM.pdf and related assets.
• National & Global Infrastructure Strategy: Strategic reports such as AI_Nation_2030_National_AI_Action_Plan_2026_2030_Eng_V_290726_49cb382621.pdf and sovereign AI digital infrastructure grids.
• External Partners & Corporate Assets: Supporting documents including Google Cloud Build files, brochures, and partnership visuals.
• System Records & Integrations: Ownership directories, partnership references like Kerjasama MSI-2026-07734, and version control logs.

Local Workflow: Clone and Access the Data Lake

To pull these resources to your local workspace, run the following commands in your terminal:
bash

Clone the repository via HTTPS

git clone https://github.com/Sazwan96/SGAE-Data-Lake.git

Move into the project root directory

cd SGAE-Data-Lake

Verify the asset mapping tree structure

ls -la
Use code with caution.
Let me know if you would like me to help you parse specific structural requirements from the project guides, generate a custom automation workflow (.yml) for tracking these data updates, or set up the workspace synchronization metadata!

[erikpinterlukacs]

Samruddhi Khandale (@samruddhikhandale) Alexandru Dima (@alexdima) There is a comment above (#464 (comment)) that looks like some sort of scam. I'm tagging you, because I couldn't find a way to report it elsewhere. Could you take a look at it when you have a chance? Thanks