Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Temporary files in a different directory #550

Closed
PiTiLeZarD opened this issue Sep 3, 2023 · 0 comments
Closed

Temporary files in a different directory #550

PiTiLeZarD opened this issue Sep 3, 2023 · 0 comments

Comments

@PiTiLeZarD
Copy link

Hi,

I haven't read the go code so apologies if this issue sprouts from my lack of understanding.

I use docker-gen in production on a docker swarm reverse proxy situation. It's worked great over 2/3 years I'm doing this. Recently I've been having an issue. All nodes in the swarm share a folder which is on azure shared blob. They all know of each other's configuration and a script combines all of these configs into one using crossplane, so ultimately they all have the same config and requests can hit any node and return something from any node.

Enough bragging, I reckon sometimes docker-gen generates a temporary file docker-gen.XXX.conf and deletes it real quick after that, but due to docker shares, and samba shares probably all adding their healthy dose of lag, maybe that file sticks around and messes up all the merging business, sites go down and I end up working on weekends and we don't want that! lol Not sure if maybe the file ends up not being deleted at all? I blame docker/samba but I'm not entirely sure.

So I was wondering if there's a way I can still point docker-gen at a folder but tell docker-gen to use /tmp for its internal workings?

Cheers

@nginx-proxy nginx-proxy locked and limited conversation to collaborators May 16, 2024
@buchdag buchdag converted this issue into discussion #617 May 16, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant