News for hackers. Stuff that matters.
Re:Unfashionably secure: why we use isolated VMs by Carrok on Thursday July 25, 2024 @05:50PM (#41073760)
> Docker actively prevents you from having a private repo.

In what ways? I use private repos daily with no issues.

Re:Unfashionably secure: why we use isolated VMs by m463 on Thursday July 25, 2024 @07:18PM (#41074448)
If you reference a container without a domain, you pull from docker.io

With podman, you can control this with

  $HOME/.config/containers/registries.conf 
or

  /etc/containers/registries.conf
with docker, not possible (though you can hack mirrors)

https://stackoverflow.com/questions/33054369/how-to-change-t...

Re:Unfashionably secure: why we use isolated VMs by Carrok on Thursday July 25, 2024 @08:09PM (#41074764)
So.. just use a domain. This seems like a nothing burger.
Re:Unfashionably secure: why we use isolated VMs by m463 on Friday July 26, 2024 @12:57AM (#41075873)
Not all dockerfiles (especially multi-stage builds) are easily sanitized for this.

think FROM python:latest or FROM ubuntu:20.04 AS build

They've put deliberate barriers in the way of using docker commands without accessing their cloud.

Re:Unfashionably secure: why we use isolated VMs by Cyph0n on Thursday July 25, 2024 @08:49PM (#41074962)
Or even easier: just fully qualify all images. With Podman:

nginx => docker.io/library/nginx

linuxserver/plex => docker.io/linuxserver/plex