-
Notifications
You must be signed in to change notification settings - Fork 106
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
Docker Swarm compatibility #55
Comments
@FinlayDaG33k this is essentially forward compatibility-related: with new features in upcoming releases, there are also new settings in the mktxp.conf / _mktxp.conf files. mktxp tries to automatically add those to existing installs using defaults, which obviously could be problematic under a read-only filesystem. For Docker Swarm / compose systems, the easiest solution is just use the configs files with all settings explicitly set. |
I see. |
@FinlayDaG33k sure it makes sense to mention in FAQ. I will at some point, or just feel free to do a PR in the meantime |
Similar to above I got the error running the example from the main howto. SOLVED docker run -v "$(pwd)/mktxp:/home/mktxp/mktxp/" -p 49090:49090 -it --rm ghcr.io/akpw/mktxp:latest
|
Hii there,
I'm trying to get
mktxp
working within Docker swarm, however, I'm running into some issues.When I try to use a volume and put my
mktxp.conf
and_mktxp.conf
inside, I get the following error because the container isn't using the default user (hence, I cannot set the proper permissions):Using a
config
however, causes the startup to fail because the program sees it as aread-only
filesystem (which is normal behaviour for a config in Docker Swarm.Having proper compatibility with Docker Swarm would be desired.
The text was updated successfully, but these errors were encountered: