A looong time ago, I tried using WebDAV for internal network use and I feel like there was an issue with it I didn’t like and stopped using it and instead went with smb. The issue miiight have been that if I was copying a file to a WebDAV server it didn’t give you a file copy progress? Can’t fully remember. Either way, does WebDAV give you a file copy progress now?
I think you’re right, I’ve since moved on to Linux for my OS, but never had a reason to use WebDAV, so haven’t had the chance to test it with Linux WebDAV clients
Neat! What proccess did you follow for building distroless? I was using buildah, mounting dir, yum installing into the mount, and exporting that container off.
Eh…the usual “FROM: alpine:edge”, pull everything in with git, change the code as needed, static compiling everything, strip dead code out of the binary, send the binary in a scratch image and then assigning a non-root user to it.
Why wrap a CLI tool in a docker container? Wouldn’t it be simpler to directly compile nyancat to multiple architectures if the goal is to make it run on all platforms?
Because I’m doing this as a “self-learning” process. Plus, docker is an excellent tool and even “silly” images like this one can give me an edge while looking for (more) jobs, so there’s that. Coding could grant me the same “edge” as well yes, but docker has “more value” since it requires you to code -AND- to have some knowledge/depth regarding typical “dockerization” processes.
Am I understanding correctly that you are building the image by copying in key elements from the host machine’s functioning nginx installation?
This is creative but not common approach to docker.
Normally software is installed following the officially documented procedure (imagine installing using apt or a shell script via RUN). Sometimes software documentation has specific recommendations to follow for containerized installs.
It’s common to have the version defined as a variable where a change in value invalidates the docker layer cache. To me it’s unclear how caching would work with your dockerfile, for example, in the event of a upgrade. You could also see how a breaking change (such as one in the paths you are copying) could run into issues with your hardcoded approach.
In the case of software like nginx, I would use the official image, mount config/cert files instead of copying, and extend in my own dockerfile if needed.
Not from the host machine, but from the official nginx image ( nginx:mainline-alpine3.18-slim ). And what it (basically) does is separate the essential commands/files inside a scratch image and gives every command a custom username tag.
A bit late but you might want to have a look at docker multi-stage build documentation which does exactly what you did (start from a base image then copying stuff from it to your own image), something like that:
Which will simplify building new images against newer “build” image newer tags easier.
btw, you were quite creative on this one! You also might want to have a look at the distroless image, the goal being to only have the bare minimum to run your application in the image: your executable and its runtime dependencies.
You’re welcome! scratch and distroless are indeed basically the same thing, scratch being the ‘official’ docker minimal image while distroless is from google - as I’m more a Kubernetes user (at home and at work) than a Docker user, I tend to think about distroless first :) - my apologies if my comment was a bit confusing on this matter.
By the way, have fun experimenting with docker (or podman), it’s interesting, widely used both in selfhosting and professional environments, and it’s a great learning experience - and a good way to pass time during these long winter evenings :)
Eh…just trying to learn some new things regarding common “dockerization”-related things, and improving its security.
If the end-goal is not learning but having an as secure container as possible, then consider Wolfi; this is a good read. If you’re interested to know its current vulnerabilities, so that you can work on resolving those; then consider Trivy as it is -to my knowledge- the industry-standard for this specific use-case.
hub.docker.com
Newest