Explore >> Select a destination
|
You are here 
|
stefano-garzarella.github.io | ||
| | | | |
blog.stalkr.net
|
|
| | | | | If you like exploitation surely you've had your own reverse or connect-back shells. Set up a listening netcat, run the payload and boom: you... | |
| | | | |
fabianlee.org
|
|
| | | | | The ability to quickly stand up a guest OS with cloud-init is most often associated with deployment of virtual machines in an IaaS like EC2 or Azure. But cloud-init is not just for remote cloud providers, and using cloud-init for local images that can be quickly deployed in KVM works great for local development and ... KVM: Testing cloud-init locally using KVM for an Ubuntu cloud image | |
| | | | |
dustymabe.com
|
|
| | | | | Recently we switched our 9p filesystem usage in CoreOS Assembler to use virtiofs. This is the technology behind a lot of new lightweight container VM technology like kata-containers and libkrun, but can also be easily used with libvirt. Running as non-root using qemu:///session Currently the virtiofs integration doesn't work as non-root via a qemu:///session connection. There is an oustanding RFE for this upstream and downstream in RHEL that can be followed for updates. | |
| | | | |
negativesign.com
|
|
| | | In my previous post I talked about how to build some Docker containers to run a deep learning-focused1 JupyterHub instance. It's nice for several reasons if the JupyterHub server brings itself up when the system starts. Here's how to do that-an adaptation of this Stack Overflow post. Create a file at /etc/systemd/system/docker-jupyterhub.service and put the following text into the file. [Unit] Description=JupyterHub container Requires=docker.service After=docker.service [Service] Restart=always ExecStart... | ||
