Live data from Hacker News

Alpine Linux Docker images have NULL for root password

cve.mitre.org

111–120 of 203 posts

Re: Alpine Linux Docker images have NULL for root password

#112

Earlier quoted context omitted.

Adding a shell seems antithetical to deploying production code as a static-linked binary, not to mention an expansion of the attack surface of the container.

Without a shell, how does one debug if anything goes wrong?

from the host system, containers don't exist in a vacuum

Re: Alpine Linux Docker images have NULL for root password

#113
post #63

Earlier quoted context omitted.

Unless you're behind a load balancer which terminates TLS and the traffic you deal with is purely http.

sure, as long as you don't connect to ANY outside url's for anything

Which you probably shouldn't be doing for most of your services anyway.

Re: Alpine Linux Docker images have NULL for root password

#114
post #34

Earlier quoted context omitted.

You might want at least a shell in the container for debugging?

Adding a shell seems antithetical to deploying production code as a static-linked binary, not to mention an expansion of the attack surface of the container.

Debugging is about when the difference between theory and practice breaks down.

Re: Alpine Linux Docker images have NULL for root password

#115
post #113
post #63

Earlier quoted context omitted.

sure, as long as you don't connect to ANY outside url's for anything

Which you probably shouldn't be doing for most of your services anyway.

I don't remember the last project I did which didn't have some sort of integration with an external service. I guess if you use microservices, most components won't need it; I mostly use monoliths.

Re: Alpine Linux Docker images have NULL for root password

#117

I have always been a bit surprised at the popularity of Alpine Linux for docker images. It’s awesome that the images are pretty small, but a wide variety of software has been shown to run noticeably slower on Alpine compared to other distributions, in part due to its usage of musl instead of glibc. I’d think that a few megabytes of disk isn’t as valuable as the extra cpu cycles.

> I’d think that a few megabytes of disk isn’t as valuable as the extra cpu cycles. Depends on your workload, of course. Some people want to run a huge number of containers and each isn’t compute intensive. Or maybe you don’t use libc at all in your fast path? Lots of cases it makes sense.

If you reuse the base image, the libc files will be shared anyway.

Re: Alpine Linux Docker images have NULL for root password

#118

Earlier quoted context omitted.

Isn't there an argument that using Alpine instead of something like Ubuntu is premature optimization for space?

It's faster in terms of development time. Faster to install packages and to push to docker repos.

Why? You should only need to push the base image once. Then only upper layers will have to be pushed.

Re: Alpine Linux Docker images have NULL for root password

#119
post #27
post #16

Earlier quoted context omitted.

Benchmarks here: https://www.phoronix.com/scan.php?page=article&item=docker-s... For Python in particular, significantly slower.

The Python test is indeed a large outlier! I wonder how reproducible it is, and what the reason might be.

That is very likely due to processor/architecture optimized precompiled Python. See e.g. https://clearlinux.org/blogs/transparent-use-library-package... and https://clearlinux.org/blogs/boosting-python-profile-guided-...

Re: Alpine Linux Docker images have NULL for root password

#120
post #58

Earlier quoted context omitted.

Because it's tiny, I tend to default to Alpine and then move away from it where necessary. Rather than worrying about potential CPU performance requirements upfront - premature optimisation and all that.

Isn't there an argument that using Alpine instead of something like Ubuntu is premature optimization for space?

Optimization is only premature when other people do it. :)
Post reply on HN