Software Development in a Container - Coding by Copy - a Primer

Containers make it easy to set up a complex data scientist development environment.  A developer can just spin up a Python, Jupyter Notebook, Spark, Hadoop, or another type of container on a local machine in minutes.

Containers can be confusing when you first work with them. Here we talk a little about how you can get code and data into your container environment and how you can get it back out.

I want to write code local to my laptop and run the code inside a fully configured Anaconda container. And, I'm lazy.

Two ways to get code onto a container for development

Containers are standalone mini machines with private disk space, CPU, networking  and other services.  They are not intended to retain state, something that we definitely want to do in a development environment. We need to get our code inside the container. We can do the same thing with data or we can have our code pull the data in at runtime.

We plan on doing all development on the container for this discussion.

There are two primary ways of getting code onto a machine.  We can push code into the container for development and execution and then pull it back out when done. 

Alternatively, we can operate from inside the container. We can pull code from a remote repository, work on it and then push the code back to the repository.

Option 1: Copy Code to and from Container from outside

Starting work using code to the container
  1. Use "docker cp local remote" to copy from your host machine or your local developer machine to the docker container
Develop code
  1. Use container IDE or IDE on "My Machine" with remote server capability like Visual Studio Code
Saving work from the container back to the local machine
  1. Use "docker cp remote local" to copy from your docker container to your local / developer machine.

Option 2: Pull into and push out code from inside the container

Starting work pulling code to the container
  1. Log into the docker container with "docker exec -it ..."
  2. Run "git pull" to pull the code from the remote repository.
Develop code
  1. Use container IDE or IDE on "My Machine" with remote server capability like Visual Studio Code
Saving work external to the container pushing the code back to the repository
  1. Run "git push" to push the code back to the repository

Video: This article


Related Content

  • http://joe.blog.freemansoft.com/2020/01/edit-build-run-in-container-with-vs-code.html
  • http://joe.blog.freemansoft.com/2021/02/software-development-in-container.html
  • http://joe.blog.freemansoft.com/2021/02/software-development-in-container_9.html

Editing content using a host IDE with remote server
We want to edit, syntax check, debug, run the programs inside the container while using a familiar IDE.   Some IDEs like Visual Studio Code can run in a split mode where the IDE runs on your local machine and a remote headless server copy runs inside the remote machine or container.  Visual studio code can install its remote server component on any machine that you have SSH access and containers where it can remote exec.

Run The IDE your local machine.  Open the remote access and edit and run the code that is actually on the remote container.  

Visual Studio Code and other IDEs support git and other repository plugins on the remote server component. This means you can open a remote session on the container and then pull down and commit your code all via the local IDE and the remote server connection.



Editing content on the Container with container-based IDE
Some development environments like Jupyter Notebooks run as a web server. You can start the notebook server in the container on container startup.  The IDE runs on the server so it can see files in that remote server's workspace.

Notebook servers tend to not have SCM integration. This means you may have to either remote shell into those machines to manipulate repositories or docker cp files into and out of the machine running the commands on your local machine.

Fini
Thanks for reading.
Created 2/2021

Comments

Post a Comment

Popular posts from this blog

Installing the RNDIS driver on Windows 11 to use USB Raspberry Pi as network attached

Image
I do a lot of my development and configuration via ssh into my Raspberry Pi Zero over the RNDIS connection. Some models of the Raspberry PIs can be configured with  gadget drivers  that let the Raspberry pi emulate different devices when plugged into computers via USB. My favorite gadget  is the network profile that makes a Raspberry Pi look like an RNDIS-attached network device.  All types of network services travel over an RNDIS device without knowing it is a USB hardware connection. A Raspberry Pi shows up as a Remote NDIS (RNDIS) device when you plug the Pi into a PC or Mac via a USB cable. The gadget  in the Windows Device Manager picture shows this RNDIS Gadget connectivity between a Windows machine and a Raspberry Pi. The Problem Windows 11 and Windows 10 no longer auto-installs the RNDIS driver that makes magic happen. Windows recognizes that the Raspberry Pi is some type of generic USB COM device. Manually running W indows Update  or  Update Driver  does  not  install the RNDI
Read more

Understanding your WSL2 RAM and swap - Changing the default 50%-25%

Image
The Windows Subsystem for Linux operates as a virtual machine that can dynamically grow the amount of RAM to a maximum set at startup time.  Microsoft sets a default maximum RAM available to 50% of the physical memory and a swap-space that is 1/4 of the maximum WSL RAM.  You can scale those numbers up or down to allocate more or less RAM to the Linux instance. The first drawing shows the default WSL memory and swap space sizing. The images below show a developer machine that is running a dev environment in WSL2 and Docker Desktop.  Docker Desktop has two of its own WSL modules that need to be accounted for.  You can see that the memory would actually be oversubscribed, 3 x 50% if every VM used its maximum memory.  The actual amount of memory used is significantly smaller allowing every piece to fit. Click to Enlarge The second drawing shows the memory allocation on my 64GB laptop. WSL Linux defaults to a maximum RAM size of 5
Read more

Almost PaaS Document Parsing with Tika and AWS Elastic Beanstalk

Image
The Apache Tika project provides a  library capable of parsing and extracting data and meta data from over 1000 file types.  Tika is available as a single jar file that can be included inside applications or as a deployable jar file that runs Tika as a standalone service. This blog describes deploying the Tika jar as an auto-scale service in Amazon AWS Elastic Beanstalk.  I selected Elastic Beanstalk because it supports jar based deployments without any real Infrastructure configuration. Elastic Beanstalk auto-scale should take care of scaling up and down for for the number of requests you get. Tika parses documents and extracts their text completely in memory. Tika was deployed for this blog using EC2 t2.micro instances available in the AWS free tier. t2.micro VMs are 1GB which means that you are restricted in document complexity and size. You would size your instances appropriately for your largest documents.   Preconditions An AWS account. AWS access id and secret key.
Read more