Skip to content
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

config file vsftpd.conf is empty when binding mount conf path #64

Open
luky83 opened this issue May 26, 2021 · 2 comments
Open

config file vsftpd.conf is empty when binding mount conf path #64

luky83 opened this issue May 26, 2021 · 2 comments

Comments

@luky83
Copy link

luky83 commented May 26, 2021

If a container is run with -v /home/ftps/vsftpd-conf/:/etc/vsftpd/ a folder with all the config file get created but the file vsftpd.conf is empty. As the container attempt to start the Variables set at container runtime section gets populated but the container crashes as the rest of the config file is missing.
I was able to start the container by editing the config file and restart.
Every time I restart the container all Variables set at container runtime are duplicated ( the file grows at each restart ).

@w570955342
Copy link

Have you solved this problem? @luky83

@luky83
Copy link
Author

luky83 commented Jul 29, 2022

I worked around the problem by copying the vsftpd.conf file back from a container created without the bind mount.
Then I launched the container with the bind mount and provided the customized conf file from the host.
Everything is working, the only problem is the vsftpd.conf file keep growing as runtime variables are appended on bottom at some intervals ( not only container restarts I suppose)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants