Docker container for remote accessible Midnight Commander file manager.
50K+
Since automated builds are not available anymore, this README will not be updated automatically, but should be up-to-date. This also means that the Github repository is no longer displayed as the source. Images are now pushed using GitLab CI so the build process logs are available there. The images are also available on GitLab so definitely use those especially if we start hitting the new Docker Hub limits.
registry.gitlab.com/kalaksi-containers/midnight-commander)docker.io/kalaksi/midnight-commander)This container runs SSH server and is configured to run Midnight Commander directly after login. So essentially this container is a remote accessible file manager.
Simply put, this container has been written with simplicity and security in mind.
Many community containers run unnecessarily with root privileges by default and don't provide help for dropping unneeded CAPabilities either. On top of that, overly complex shell scripts, monolithic designs and unofficial base images make it harder to verify the source among other issues.
To remedy the situation, these images have been written with security and simplicity in mind.
| Requirement | Status | Details |
|---|---|---|
| Don't run as root | ❌ | OpenSSH 7.5 makes privilege separation mandatory which requires root, but those privileges are dropped. TODO: Maybe change to some other SSH-server? |
| Transparent build process | ✅ | For verifying that the container matches the code. See GitLab CI. |
| Official base image | ✅ | |
| Drop extra CAPabilities | ✅ | See docker-compose.yml |
| No default passwords | ✅ | No static default passwords. That would make the container insecure by default. |
| Support secrets-files | ✅ | Support providing e.g. passwords via files instead of environment variables. |
| Handle signals properly | ✅ | |
| Simple Dockerfile | ✅ | No overextending the container's responsibilities. And keep everything in the Dockerfile if reasonable. |
| Versioned tags | ✅ | Offer versioned tags for stability. |
See the example docker-compose.yml in the source repository.
The username for connecting the container is mc.
See the Tags tab on Docker Hub for specifics. Basically you have:
latest tag that always has the latest changes.1.1 which would follow branch 1.1.x on GitHub.See Dockerfile and docker-compose.yml (https://github.com/kalaksi/docker-midnight-commander) for usable environment variables. Variables that are left empty will use default values.
To modify sshd configuration, modify the sshd_config file located in the midnight-commander-volume.
To modify Midnight Commander configuration, you can bind-mount over the configuration files under /home/mc/.config/mc.
See the repository on https://github.com/kalaksi/docker-midnight-commander. All kinds of contributions are welcome!
Copyright (c) 2018 [email protected]. See LICENSE for license information.
As with all Docker images, the built image likely also contains other software which may be under other licenses (such as software from the base distribution, along with any direct or indirect dependencies of the primary software being contained).
As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.
Content type
Image
Digest
sha256:2860836e7…
Size
11.3 MB
Last updated
3 months ago
docker pull kalaksi/midnight-commander