⚠︎ Архивная вакансия
Эта вакансия была перемещена в архив. Возможно она уже не актуальна и рекрутер больше не принимает отклики на эту вакансию. Вы можете  найти актуальные похожие вакансии

Docker Core Specialist

Вакансия в   SUSE Linux GmbH ( www.suse.com )
Аккаунт зарегистрирован с публичной почты *@gmail.com, не email компании!
5 февраля 2016
Удаленная работа
Опыт работы любой
Работодатель  SUSE Linux GmbH
Описание вакансии
Job location: Virtual Office or any SUSE location
SUSE Linux Enterprise has shipped container technology for years. Since SUSE Linux Enterprise 12 we also offer a technical preview of Docker, which we believe will play a major role in application deployment.We want to help our customers orchestrate Docker containers running on a distributed system. Responsibilities
  • You will work on the system-level components of the container engine (Docker), touching the kernel and storage subsystems in order to improve reliability and security
  • You will develop features on Docker and its tools required by SUSE Linux Enterprise and other SUSE products
  • You will write, upstream and backport patches in order to keep Docker and our orchestration system stable and secure
  • You will to work on a bare version of SUSE Linux Enterprise focused on running Docker containers
  • You will influence the future of the Docker and its orchestration solution code-base, working with upstream and influencing design and implementation decisions
  • You will also work with users to identify problems and opportunities, turn them into good bug reports, track progress, and provide feedback back to users
Qualifications & Required Skills
  • Experienced systems developer with deep understanding of the Linux Operating System and its low level interfaces (e.g. kernel namespaces, cgroups, C, POSIX)
  • Comfortable about writing and upstreaming kernel patches and interacting with kernel developers
  • Passionate about programming and creating excellent software which meets the goals of its users
  • Team player. Autonomous and results oriented work style
  • Proficient in English
  • Understanding Open Source development processes and culture
  • You're passionate about continuous integration, test driven development and are used to write automated tests for your code
  • You know the obstacles of actual deployment and how to handle them
  • Experience with development on Linux and related tools: gcc, gdb, git
  • Experience with scripting languages (eg. Python, Perl, Ruby)
  • Familiarity with Docker orchestration solutions (eg. Docker swarm, fleet, Kubernetes) Familiarity with Docker and its ecosystem
  • Familiarity with packaging software for Linux (eg. rpm, deb) is a plus
  • Familiarity with the Go language is a plus 
Our Offer
  • Direct contact with representatives of free/open source software projects worldwide
  • Regular hackathons (Hack Weeks) and workshops on the company, department, and team levels
  • Five weeks vacation (*)
  • Contributions to pension insurance or capital life insurance (*) Other common employee benefits (food coupons, health care, sports and cultural activities) (*) Free beverages (*) We know how to party!
  • We celebrate success
(*) Reference for the example benefits is the office in Germany. They may vary across hiring locations REQUIRED WITH APPLICATION, Challenge: Choose one and point us to it in your application.
Please provide a link to at least one of the following challenges together with your application. It can be a URL, Git repository or a Github Pull Request depending on the challenge. You can send your application as soon as you sent your link, Pull Request or git repository and then continue interacting with the developers while your application is reviewed. Challenge #1 Run latest version of Docker on openSUSE 13.2 and try to build a new image using Docker’s build system. Introduce an error inside of the Dockerfile and then start the build. You will end up with an image with “” as name.You can use the following Dockerfile to reproduce the issue: FROM busybox RUN touch /hello RUN boom Try to debug the problem, and guide us through the code flow that produces this and your debugging process. Challenge #2 Write a tool which shows information about the images available on a Docker host (eg: which layers are shared between the images, parent-child relationships between images, …).As a plus ALSO show if there are layers which are no longer relevant on the machine (like the ones produced when running a Docker container without the “--rm” option). Challenge #3 Write a plugin or your choice for Docker using the new plugin system. Challenge #4 Have you already contributed to Docker? Great, point us to a PR or commit you contributed or took part.