Sixth Post!

[hoisinsauce]

"The thing about illegally breeding fire-breathing possums is that you gotta keep a bucket of water handy."

*Those fools! Fire-breathing possums are greasy; water will only feed the flames! Oh, if only I could tell them of my empire...*

(Context: https://secretfanspace.dreamwidth.org/1839.html?thread=2678831#cmt2678831)

Talk fandom! Making things! Reading, writing, drawing, whatever! Miscellaneous life chatter! Meme's happy to see you again!

(start a comment thread by replying to this post)

Comments

Re: Coding

[(Anonymous)]

Colleague: ... and maybe we can just build this in the container from now on!

More experienced colleague: I don't think it will be so simple, because the build process creates a VM for some steps.

Colleague: I can try it and see what happens!

More experienced colleague: I mean if you want to but...

Other colleague: That'll be great, if we can do it all in the container, we'll need so much less infra!

More experienced colleague: *gives up*

Re: Coding

[(Anonymous)]

I haven't done much coding in this area before, so am trying to figure out: is it possible? Tentative yes but it'll cause more work rather than saving any?

Re: Coding

[(Anonymous)]

Possible but probably silly, yeah. Nesting things like that is generally not great because it's slow and when something goes wrong it's a pain to debug, and then doing it 'vm in container' rather than 'container in vm' is even more strange. Wondered if anyone had a reason for doing it and found a blogpost:

https://medium.com/axon-technologies/installing-a-windows-virtual-machine-in-a-linux-docker-container-c78e4c3f9ba1

(I didn't look closely but the bit about how much room VMs take up looks a bit odd; you normally set a max size rather than a fixed size and I think you could have them use the same image. some randomers on stackoverfow seem to concur: https://stackoverflow.com/questions/40559577/create-multiple-vms-based-on-single-image .)