# config.vm.synched_folter './data'', '/vagrant_data'Ĭonfig.vm.provision :docker_compose, yml: '/vagrant/docker-compose.yml', rebuild: true, run: 'always' # config.vm.network 'forwarded_port', guest: 80 host: 8080 Offset = DateTime.parse(machineTime).strftime('%Q').to_i - ('%Q').to_i Vagrantfile: nfigure('2') do |config|Ĭonfig.vm.define 'ubuntuvm' do |ubuntuvm| The corresponding docker-compose provisioner takes care of automatically running the docker-compose.yml. The Vagrantfile below resets the datetime of the vm to a specific one, before the machine goes up. My solution: I run docker on top of a virtualbox vm via vagrant. This terminates your screen and tty session.This uses the server defined in /etc/ntp.conf (this looks like a magic bridge back to the host clock).This detaches the screen session, but leaves the tty running.It’s not quite the same as other date implementations. You canĪlso use other formats, look for documentation on “busybox date” as All of your docker containers will now have your new time.The screen starts blank, hit enter a few times.screen ~/Library/Containers//Data/64-linux/tty.You can't set the date of your host machine.OPTION 2: Change the date of the Alpine VM Run this sequence again to get back to the right date & time. Change the date of your machine via the Date & Time Preferences.You can change the date of your host machine.OPTION 1: Change the date of your host machine & restart docker I found the following options work on Mac, but you have to realize you'll be changing the date for all of your containers because you're changing the date of the underlying Alpine VM that Docker uses for all of its containers.

For me, I actually needed to set the actual date for testing.

Set date