You can use the following command to run a terraform apply using the current directory as the volume. This is great if you, say, do a git checkout of your repository and want to just run the terraform files from the checkout folder.
docker run -it -v $(pwd):/workpace -w /workpace hashicorp/terraform:light apply
I manage a few decent sized Jupyter Hub environments based on the docker spawner. Each frequently has more than 50 users, sometimes much more…. and recently, one of the servers ran out of memory.
I have some read-only notebooks inside the user containers… so I figured that if a user only had those read only notebooks, I could shut down their docker containers. They weren’t doing any work that could be lost.
So, I wrote this script to:
I hope it helps you with a similar docker-related issue! 🙂
CONTAINERS=`docker container ls | awk '{print $14}'`
for NAME in ${CONTAINERS}
do
#echo $name
COUNT=`docker exec ${NAME} ls -a | grep .ipynb | grep -v checkpoints | wc -l`
if [[ $COUNT = 1 ]];
then
echo "Stopping $NAME with COUNT = $COUNT."
docker container stop $NAME;
fi
done
There is probably a much cleaner way of doing this using off-the-shelf automations. But I was just following along with the AWS installation instructions and got this working.
- name: Download AWS CLI bundle. shell: "cd /tmp && rm -rf /tmp/awscli* && curl 'https://s3.amazonaws.com/aws-cli/awscli-bundle.zip' -o 'awscli-bundle.zip'" - name: Update repositories cache and install "unzip" package apt: name: unzip update_cache: yes - name: Unzip AWS CLI bundle. shell: "cd /tmp && unzip awscli-bundle.zip" - name: Run AWS CLI installer. shell: "/tmp/awscli-bundle/install -i /usr/local/aws -b /usr/local/bin/aws" - name: Log into aws ecr docker registry when: jupyterhub__notebook_registry != '' shell: "$(/usr/local/bin/aws ecr get-login --no-include-email --region us-east-1)"
In order to do the actual login, you need to ensure your EC2 instance has an IAM role assigned to it that has reader privileges. Then you should be all good!
I was trying to run ansible over a debian slim docker image and I got this error, which was rather cryptic. There wasn’t any particularly good information on google for fixing it either.
ContextualVersionConflict: (cryptography 1.7.1 (/usr/lib/python2.7/dist-packages), Requirement.parse(‘cryptography>=2.5’), set([‘paramiko’]))
ERROR! Unexpected Exception, this is probably a bug: (cryptography 1.7.1 (/usr/lib/python2.7/dist-packages), Requirement.parse(‘cryptography>=2.5’), set([‘paramiko’]))
the full traceback was:Traceback (most recent call last):
File “/usr/local/bin/ansible-playbook”, line 97, in <module>
mycli = getattr(__import__(“ansible.cli.%s” % sub, fromlist=[myclass])…
In my case, running this before my ansible install resolved the issue. It just forces an upgrade to a newer version which ansible is okay with. Of course, if you were dependent on the lesser version this may not be an option.
pip install –force-reinstall cryptography==2.7
First, just start by getting a root shell so we can drop the sudo command from everything (e.g. type sudo bash). This isn’t best practice, but just make sure you exit out of it when you are done :).
Note that this installs wget, OpenJDK Java 1.8, Jenkins, enables Jenkins to be on with system start, and then it installs docker, and finally, it adds the Jenkins user to the docker user group so that it can run commands from it effectively (using elevated privileges). Lastly, it restarts Jenkins so that the user has the new docker group permissions in the running process.
yum update -y
yum install wget -y
yum install java-1.8.0-openjdk-devel -y
wget -O /etc/yum.repos.d/jenkins.repo http://pkg.jenkins-ci.org/redhat-stable/jenkins.repo
rpm –import https://jenkins-ci.org/redhat/jenkins-ci.org.key
yum install jenkins -y
service jenkins start
chkconfig jenkins on
yum install -y yum-utils device-mapper-persistent-data lvm2
yum-config-manager –add-repo https://download.docker.com/linux/centos/docker-ce.repo
yum install -y docker-ce docker-ce-cli containerd.io
systemctl start docker
usermod -a -G docker jenkins
service jenkins restart
Assuming this all worked, you should see Jenkins running on your localhost:8080 port for that server, and you can follow its on-screen instructions.
For docker, you can run the hello world container to see if it is properly set up (docker run hello-world).
I got this information from the Jenkins wiki, the docker site itself, and one stack overflow entry as shown below:
Coding Stream of Consciousness 