-
-
Notifications
You must be signed in to change notification settings - Fork 325
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
The container doesn't support user chrooting #2
Comments
Hi @lpereir4, Also yes my demo command in the README if for a chrooted account to a specific folder, this is just a demo showing its usage, but i've now updated the doc's to say that this is a chrooted example. |
Hi @stilliard, My host distribution is CentOS 7. I used the makefile and followed the README for user creation.
Both command line ftp client and filezilla fails to connect :
|
Just double checking, the pure-pw commands, they have been run inside the docker container, not on the |
inside the docker container of course. |
Cool, just double checking as i've repeated the steps myself but i'm still |
Indeed, the directory has been created. |
Strange, one other check, is the user ftpuser setup in the container, it should already be as its built from the dockerfile? The only other thing i can suggest is to try pulling from the hub repo rather than building from here:
I just followed the above process to double check and that worked for me. |
Pulling from the hub works. |
Closing as I believe this is now resolved. |
The use of '-d /home/ftpusers/bob' (user chrooting) results in having this error when attempting to log in :
421 Home directory not available - aborting
If you do not intend to allow chrooting please update documentation (use of -D instead of -d)
The text was updated successfully, but these errors were encountered: