<commit_before>FROM boot2docker/boot2docker

# Customize for Vagrant
RUN mkdir -p /rootfs/home/docker/.ssh
RUN chmod 0700 /rootfs/home/docker/.ssh
RUN chown -R 1000:50 /rootfs/home/docker/.ssh
RUN echo "ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA6NF8iallvQVp22WDkTkyrtvp9eWW6A8YVr+kz4TjGYe7gHzIw+niNltGEFHzD8+v1I2YJ6oXevct1YeS0o9HZyN1Q9qgCgzUFtdOKLv6IedplqoPkcmF0aYet2PkEDo3MlTBckFXPITAMzF8dJSIFo9D8HfdOV0IAdx4O7PtixWKn5y2hMNG0zQPyUecp4pzC6kivAIhyfHilFR61RGL+GPXQ2MWZWFYbAGjyiYJnAmCP3NOTd0jMZEnDkbUvxhMmBYSdETk1rRgm+R4LOzFUGaHqHDLKLX+FIPKcF96hrucXzcWyLbIbEgE98OHlnVYCzRdK8jlqm8tehUc9c9WhQ== vagrant-insecure-public-key" > /rootfs/home/docker/.ssh/authorized_keys
RUN chmod 0600 /rootfs/home/docker/.ssh/authorized_keys

# Include rsync
RUN cp /usr/bin/rsync /rootfs/usr/bin/rsync
RUN cp /lib/x86_64-linux-gnu/libattr.so.1 /rootfs/lib/libattr.so.1
RUN cp /lib/x86_64-linux-gnu/libacl.so.1 /rootfs/lib/libacl.so.1
RUN cp /lib/x86_64-linux-gnu/libpopt.so.0 /rootfs/lib/libpopt.so.0

# Install nanobox-server
RUN mkdir -p /rootfs/var/nanobox
# Just having the nanobox-server binary on the filesystem seems to cause a kernel panic on boot (linux hosts)
RUN echo "none" > /rootfs/var/nanobox/nanobox-server.md5<commit_msg>Include ipvsadm in boot2docker<commit_after>FROM boot2docker/boot2docker

# Customize for Vagrant
RUN mkdir -p /rootfs/home/docker/.ssh
RUN chmod 0700 /rootfs/home/docker/.ssh
RUN chown -R 1000:50 /rootfs/home/docker/.ssh
RUN echo "ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA6NF8iallvQVp22WDkTkyrtvp9eWW6A8YVr+kz4TjGYe7gHzIw+niNltGEFHzD8+v1I2YJ6oXevct1YeS0o9HZyN1Q9qgCgzUFtdOKLv6IedplqoPkcmF0aYet2PkEDo3MlTBckFXPITAMzF8dJSIFo9D8HfdOV0IAdx4O7PtixWKn5y2hMNG0zQPyUecp4pzC6kivAIhyfHilFR61RGL+GPXQ2MWZWFYbAGjyiYJnAmCP3NOTd0jMZEnDkbUvxhMmBYSdETk1rRgm+R4LOzFUGaHqHDLKLX+FIPKcF96hrucXzcWyLbIbEgE98OHlnVYCzRdK8jlqm8tehUc9c9WhQ== vagrant-insecure-public-key" > /rootfs/home/docker/.ssh/authorized_keys
RUN chmod 0600 /rootfs/home/docker/.ssh/authorized_keys

# Include rsync
RUN cp /usr/bin/rsync /rootfs/usr/bin/rsync
RUN cp /lib/x86_64-linux-gnu/libattr.so.1 /rootfs/lib/libattr.so.1
RUN cp /lib/x86_64-linux-gnu/libacl.so.1 /rootfs/lib/libacl.so.1
RUN cp /lib/x86_64-linux-gnu/libpopt.so.0 /rootfs/lib/libpopt.so.0

# Include ipvsadm
RUN apt-get update && apt-get install ipvsadm
RUN cp /sbin/ipvsadm /rootfs/sbin/ipvsadm
RUN cp /lib/x86_64-linux-gnu/libnl-genl-3.so.200 /rootfs/lib/libnl-genl-3.so.200
# RUN cp /lib/x86_64-linux-gnu/libnl-3.so.200 /rootfs/lib/libnl-3.so.200

# Install nanobox-server
RUN mkdir -p /rootfs/var/nanobox
# Just having the nanobox-server binary on the filesystem seems to cause a kernel panic on boot (linux hosts)
RUN echo "none" > /rootfs/var/nanobox/nanobox-server.md5
{'fraction_non_alphanumeric': 0.09903560830860535, 'fraction_numerical': 0.07307121661721068, 'mean_word_length': 5.6265356265356266, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 7, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4588720', 'n_tokens_mistral': 1472, 'n_tokens_neox': 1325, 'n_words': 170}