Search results for query: docker

Would you mind to elaborate? If you meant that I shall stop using Docker and use Bastille BSD - because it's X & Y - I would consider that, but only once at least 70% of the ready to use apps for which I have no special requirements or that has been packed in Docker would migrate to whatever...

> Just install podman and try docker-compose. If I won't find any ready to use recipe - that's what I will do for sure. > "docker image built on a linux system" Good point, thanks - I never do docker build on the server, so it's only a question of `docker run` > I'm guessing docker-compose...

With containers the kernel is shared., so any translation is done by the Linuxulator if you're running Linux images. Just install podman and try docker-compose.

linux_enable, linux service I think are for "running prebuilt linux executables on a FreeBSD system, aka Linuxulator". Docker images should not need that, even if you have a "docker image built on a linux system". I'm guessing docker-compose is creating a docker image from a "spec", a different...

...some hands-on experience with that :) Or at least, some theory, like, for example: sysrc linux_enable="YES" service linux start pkg install docker docker-compose debootstrap # I'm incompatible with RedHat's stuff debootstrap jammy /compat/ubuntu # not sure if it's needed for Docker? cd...

podman supports docker-compose. Haven't tried it on FreeBSD, though.

pkg search docker shows "docker -18.09", docker-compose, docker-machine plus a few more

I was (and still) looking for the way to run any docker service. That is the biggest benefit of Docker - for the cases when you don't care and you just need that something to be running - it is perfect. And I have quite plenty of those things. So my perfect solution would be, if possible, to...

Instead of trying to crowbar docker services into FreeBSD, why not just install those services directly on FreeBSD? Don't know which services you need but they might run natively on FreeBSD.

Hey, I wanted to understand what is the state of Linux dockers execution and docker's compose.yaml on FreeBSD. I've tried to read various articles and that forum thread, but I'm still not sure I understand if there is some easy way to start ready to use Linux Dockers? Ideally, by re-utilizing...

...and all the other benefits hypervisors brought us were available in FreeBSD all along. Now it was 2014 and everyone was talking about Docker, Kubernates, and micro services; but again, the benefits of these systems were already available in the BSD world. So after experimenting with jails...

So the idea was that dynamic libraries are loaded *once* and shared by multiple processes. Only if they are the same version. AppImage/Snaps/Docker/etc provide different instances of the same dynamic library, of different versions. So in many ways this has proven that static linking (as is done...

This is what Golang & Docker did. But static & shared have all their pros and cons. And we're also talking about interpreted languages dependencies. Packaging Python dependencies is a nightmare.

...propose instead of the usual suspects that their junior developers (really just analysts with python knowledge) were leaning towards (AppImage/Docker/Snaps). But luckily they moved away from Linux entirely. So ultimately, even if no static linkage; just bundle the damn libs and run that in a...

...linked libraries and package managers do. I always found that very odd, how the same people critical of static linking are fine pushing Docker. They claim it's bad, difficult to update, inefficient, and insecure to build the binaries in that way. Yet it's totally fine to ship a copy of...

You can run vulnerable software in jails: it is not as convenient because you have to create the jail and compile the application, but it is more isolated. I had not read it, so everyone was happy, :) .

Correct me if I'm wrong but a sandboxed AppImage still has access to the user's home directory, no? That makes the isolation mostly useless. That makes occasionally living with vulnerable libraries a chore. Let's say libfoo-1.0 is vulnerable and libfoo-1.1 is fixed. You start out with 6 copies...

...more easily and then you don't even have to have those (maybe one day) vulnerable libraries installed in the system at all. And if the AppImage is not run as service (*cough* docker *cough*) I can live with running the vulnerable libraries from time to time from inside an image, maybe even...

...(I installed 14.3-RELEASE), I'm exploring jails (through bastille), to see if I can replicate my home server setup that I have with Linux and docker. So far so good, most everything is setup and working, but I have a very tiny question. I'm installing software through "pkg" in my jails. I...

Whatever it takes to get Docker support. A good sound system Linux would steal. Send two of the three firewalls to ports.