how can I set the working directory in old version of docker in the run command?

I am a bit new to docker and I have been trying to run deploy a meteor container with my meteor application. I have been using the dockerfile and instructions from

However, I cant run docker run -p 3000:3000 -t -i -v /path/to/meteor/app:/opt/application -w /opt/application meteor-dev because my docker (version 0.5.3) does not recognize the flag (-w) to set the working directory.

  • docker-compose remove services on exit (or recreate on start)
  • Migration from MySQL to postgresql using Django and Docker - relation “authtoken_token” does not exist
  • Dockerize your Angular NodeJS application
  • how to provide environment variables to AWS ECS task definition?
  • How to provide user defined argument and value in docker run?
  • Docker container access to local DNS
  • Is there some workaround to set the working directory with docker 0.5.3? The work directory is already set in the docker file, but I guess I need to set it again when I run the container.

  • port redirect to docker containers by hostname
  • Docker port uncertainty
  • How to cat a file inside a docker image?
  • Connect docker containers directly to host subnet
  • Why Docker/Containers has it's own networking concept(CNM/CNI) instead of using VM networking?
  • Why do ping packets not reach a custom gateway in docker?
  • One Solution collect form web for “how can I set the working directory in old version of docker in the run command?”

    well, my workaround was to create a bash script that would go to the working directory and call the commands one by one. I created the bash script where my source is located “/path/to/meteor/app” and call docker run -p 3000:3000 -t -i -v /path/to/meteor/app:/opt/application meteor-dev bash /opt/application/ with the bash as command and my script as argument

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.