|
MALE SHOEGAZE posted:i am pretty sure most of us know the basics of using docker and only one person in here was ever like 'hey does this switch mean docker is based on alpine now??' which it obviously does not. speak for yourself
|
# ? Feb 6, 2016 22:35 |
|
|
# ? Jun 13, 2024 06:04 |
|
obviously not
|
# ? Feb 6, 2016 22:35 |
|
It's not like half the posters in the Android thread have used Android or half the posters in the security thread know the first thing about security, why hold this thread to a higher standard?
|
# ? Feb 6, 2016 22:46 |
|
Cocoa Crispies posted:pram are you restocking the soda fountain at work because you are grasping at straws p. hard here lol
|
# ? Feb 6, 2016 23:15 |
|
ive never used docker its like linux vms that arent vms....but not kvm????????
|
# ? Feb 6, 2016 23:15 |
|
MALE SHOEGAZE posted:most people know apt and there for most people were easily able to start building images without starting from, well, scratch. i apt-get youre on the spectrum
|
# ? Feb 6, 2016 23:18 |
|
mishaq posted:ive never used docker linux containers are chroots specifically it's a chroot that is also using kernel namespacing + cgroups to look less like a chroot see also: solaris containers, freebsd jail(8)
|
# ? Feb 6, 2016 23:24 |
|
docker goes two steps further than just lxc's enhanced chroots
|
# ? Feb 6, 2016 23:25 |
|
Cocoa Crispies posted:someone here doesn't understand docker and it's not me It's me. However somewhere I have read about someone abusing Docker for OS containers, but that may be just LXC. MrMoo fucked around with this message at 23:39 on Feb 6, 2016 |
# ? Feb 6, 2016 23:37 |
|
you can run an init system and multiple processes in a docker container lol. there are images specifically built for that purpose http://phusion.github.io/baseimage-docker/ and guess what: you use apt to install the packages inside the container. like a normal vm or container. shocking i know
|
# ? Feb 6, 2016 23:40 |
|
pram posted:you can run an init system and multiple processes in a docker container lol. there are images specifically built for that purpose i wouldn't be surprised if that's what the future of containers, merited or not
|
# ? Feb 7, 2016 00:25 |
|
with every compile step chained into a single run command, lol
|
# ? Feb 7, 2016 00:27 |
|
i have used docker as an "os container" a lot. it's super handy for jenkins slaves
|
# ? Feb 7, 2016 00:39 |
|
i get more fps on xcom 2 on linux with open gl than with dx on windows it truly is the year of linux on the desktop
|
# ? Feb 7, 2016 00:52 |
|
docker is also loving awful you usually have some form of service discovery on the host, and docker running in bridged mode. e.g. airbnb has smartstack / synapse where service discovery is done by haproxy running on the docker host so how do you find the IP address of the host so your container can access? clearly docker should have some form of API the container can query, or maybe put an entry in /etc/hosts https://docs.docker.com/engine/reference/commandline/run/#add-entries-to-container-hosts-file-add-host you run some lovely awk command obviously this doesn't work with managers like docker-compose, kubernetes, mesos. other problems: docker's logging solution is awful. the current only solution is that every line of stderr/stdout is wrapped into syslog, so anything structured or multiline like python exceptions can't be done, even though you can normally stuff them into syslog. clearly, when you're writing a robust system deployment service, one thing you're sure of is that you can easily make sure that the only images you're using are on disk, otherwise your disk fills up really quickly. nope, docker just shits images all over your disk and doesn't clean them up, and the documented way of cleaning them up is racy and might delete layers mid-pull
|
# ? Feb 7, 2016 01:20 |
|
docker also has the appearance of not loving caring and closing pretty major issues https://github.com/docker/docker/issues/332 https://github.com/docker/docker/issues/2267 https://github.com/docker/docker/issues/12997 https://github.com/docker/docker/issues/6094
|
# ? Feb 7, 2016 01:27 |
|
|
# ? Feb 7, 2016 01:29 |
|
BobHoward posted:2016 year of spergs gettin angry bout linux containers, but not on the desktop
|
# ? Feb 7, 2016 01:33 |
|
Celexi posted:i get more fps on xcom 2 on linux with open gl than with dx on windows it truly is the year of linux on the desktop Nice!
|
# ? Feb 7, 2016 01:44 |
|
Suspicious Dish posted:docker also has the appearance of not loving caring and closing pretty major issues
|
# ? Feb 7, 2016 02:54 |
|
Only a blockhead cudgels his brains on his own, or together with a group, to "find solution" or "evolve an idea" without making any investigation. It must be stressed that this cannot possibly lead to any effective solution or any good idea. In other words, he is bound to arrive at a wrong solution and a wrong idea. When they come across difficult problems, quite a number of people simply heave a sigh without being able to solve them. They lose patience and post in the bug tracker that they "have not the ability and cannot do the job"; These are cowards' words. Just get moving on your two legs, go the rounds of every source file in the repository and "inquire into everything" as Linus did, and then you will be able to solve the problems, however little is your ability; for although your head may be empty before you go out of doors, it will be empty no longer when you return but will contain all sorts of material necessary for the solution of the problems, and that is how problems are solved. Must you go out of doors? Not necessarily. You can call a brainstorming meeting of people familiar with the situation in order to get at the source of what you call a difficult problem and come to know how it stands now, and then it will be easy to solve your difficult problem. Whatever is implemented in Unix is right — such is still the mentality of technically backward software peasants. Strangely enough, within the free software leadership there are also people who always say in a discussion, "Show me where it's implemented in Unix." When we say that the design of a Unix component is correct, that is not just because it is "a Unix component" but because its features conform with both the objective and subjective circumstances of the application and meet its requirements. When we say Unix is correct, it is certainly not because Thompson and Ritchie were "prophets" but because their concepts have been proved correct in practice and deployment. In our acceptance of their design no such formalisation of mystical notion as that of "prophecy" ever enters our minds.
|
# ? Feb 7, 2016 03:06 |
|
Gazpacho posted:Only a blockhead cudgels his brains on his own, or together with a group, to "find solution" or "evolve an idea" without making any investigation. It must be stressed that this cannot possibly lead to any effective solution or any good idea. In other words, he is bound to arrive at a wrong solution and a wrong idea. Source your quotes
|
# ? Feb 7, 2016 05:26 |
|
BobHoward posted:2016 year of spergs gettin angry bout linux containers, but not on the desktop I thought containers were the future of desktop Linux, so every "app" actually had a full collection of all the libraries and daemons and so on above the base X11/Wayland poo poo that it relied on that way Linux can continue its pathological avoidance of any attempt to treat mid-1970s technology (like a window system) as something an OS should just provide a single version of and expect all applications to be built on top of
|
# ? Feb 7, 2016 05:46 |
|
I should probably learn to use docker but I don't see the point right now. seems like a pain in the rear end to setup networked poo poo. is there anything to control docker like virtual box? I don't want to learn another cli utility, I've hit my threshold for the week. you can give containers their own bridged interface into the network right? unique ip and all?
b0red fucked around with this message at 05:58 on Feb 7, 2016 |
# ? Feb 7, 2016 05:48 |
|
docker seems kinda bad. how hosed does your packaging and deployment story have to be that a slightly gussied-up copy-paste job of your base os for every service you want to run starts to look like a good idea naturally you should use some sort of configuration management software to store all of your server configs in git as opposed to setting it up by hand like some sort of caveman. but you can still keep everything in the same filesystem namespace.
|
# ? Feb 7, 2016 05:57 |
|
Mr Dog posted:docker seems kinda bad. how hosed does your packaging and deployment story have to be that a slightly gussied-up copy-paste job of your base os for every service you want to run starts to look like a good idea the badness is much deeper than that the docker model encourages people to generate, keep, and distribute "golden images" using what are essentially shell scripts. it is a colossal step backwards for configuration management they found a cute trick with aufs and decided to make that the core feature of the product
|
# ? Feb 7, 2016 06:02 |
|
docker, as a distribution model, should be a caching layer. you cache images generated by configuration management because they're expensive to generate. no layers no faux-shell "Dockerfile" replace that poo poo with careful puppet/chef/ansible integration
|
# ? Feb 7, 2016 06:03 |
|
lennart's package vision looks suspiciously similar to what the GNU hurd was supposed to accomplish (returning admin power to the users), except that i believe he and his buds might be able to pull it off
Gazpacho fucked around with this message at 06:09 on Feb 7, 2016 |
# ? Feb 7, 2016 06:06 |
|
hey yospos I need some peer pressure to actually verify Wine in Ubuntu 16.04 will be a reasonable package cause I've been shirking Ubuntu duties for the greater part of a year now
|
# ? Feb 8, 2016 02:49 |
|
Lol wine will always be terrible. Sorry.
|
# ? Feb 8, 2016 02:58 |
|
ShadowHawk posted:hey yospos I need some peer pressure to actually verify Wine in Ubuntu 16.04 will be a reasonable package cause I've been shirking Ubuntu duties for the greater part of a year now Ask the playonlinux boyz, they're pretty up to date
|
# ? Feb 8, 2016 03:07 |
|
theultimo posted:Ask the playonlinux boyz, they're pretty up to date Other things have filled into the niche there. But at this rate there won't even be a good stable package in the LTS release unless I do something.
|
# ? Feb 8, 2016 03:30 |
|
ratbert90 posted:Lol wine will always be terrible. Sorry. actually it's good
|
# ? Feb 8, 2016 03:32 |
|
To respond to this from a while back:pram posted:i think GNU is the missing element from this discussion about why linux is ubiquitous and bsd is dead (netcraft confirms)
|
# ? Feb 8, 2016 03:34 |
|
ratbert90 posted:Lol wine will always be terrible. Sorry.
|
# ? Feb 8, 2016 03:35 |
|
theultimo posted:Ask the playonlinux boyz, they're pretty up to date Trigger warning please
|
# ? Feb 8, 2016 03:59 |
|
ShadowHawk posted:To respond to this from a while back: The traditional argument says GPL is the license for people who want to get paid to write software, BSD is the license for people who already are/were.
|
# ? Feb 8, 2016 04:21 |
|
without the 90s computer tech boom linux would have been forgotten
|
# ? Feb 8, 2016 04:30 |
|
look at the usenet archives and tell me people weren't ideological about 80s unix
|
# ? Feb 8, 2016 04:31 |
|
|
# ? Jun 13, 2024 06:04 |
|
i love linux
|
# ? Feb 8, 2016 07:32 |