[Bug]: Setting Consistent Container Names to true still uses bad container names under the hood

[dickermoshe]

Description

I've set Consistent Container Names to true so that I can run commands in a single container of my docker compose deployment.

However when running with what should be the consistent name web-o0og8ko it fails

ScheduledTaskJob failed: No valid container was found. Is the container name correct?

SSHing into the machine I see that the name is actually c8kckc8-web

This is only affecting Scheduled jobs though, one-off tasks still use the web-o0og8ko name.

Btw, should paying customers be filing bugs, or contacting another way?

Minimal Reproduction (if possible, example repository)

N/A

Exception or Error

No response

Version

v4.0.0-beta.273

[hkd987]

#2053 -> Seeing a similar issue as well

[andrasbacsai]

Btw, should paying customers be filing bugs, or contacting another way?

Anyone can fill bugs.

To your issue, what kind of deployment type do you use? Docker compose / dockerfile / nixpacks, etc.

[dickermoshe]

Dockerfile and Docker Compose. It has a larger impact on compose because scheduled task don't require a name be specified for a single container However on both the name of the Docker container when running docker ps isn't the correct name.

…

On Tue, May 14, 2024, 6:47 AM Andras Bacsai ***@***.***> wrote: Btw, should paying customers be filing bugs, or contacting another way? Anyone can fill bugs. To your issue, what kind of deployment type do you use? Docker compose / dockerfile / nixpacks, etc. — Reply to this email directly, view it on GitHub <#2122 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASDJ625FHF2TICC7DUD7BTTZCHTULAVCNFSM6AAAAABHEHEXUKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBZHA4DAMBRGU> . You are receiving this because you authored the thread.Message ID: ***@***.***>