blog.devgenius.io – Although there are different ways to install a Kubernetes cluster especially the managed ones within cloud platforms, still there are cases when we need to have it on bare metal in a DC. Thus…
Quelle: news.kubernauts.io
Starting with Docker Desktop 4.4.2 we’re excited to introduce a new authentication flow that will take you through the browser to sign in, simplifying the experience and allowing users to get all the benefits of autofill from whatever browser password manager they may use. Gone are the days of going to your browser, opening your password manager, finding your Docker password, copying, and then returning back to the dashboard or command line to paste it in (maybe I’m alone here, but I can never remember my passwords on my own!).
As part of this authentication change, we’ve also introduced Single Sign-on for users with a business subscription that enables benefits such as automated and secure onboarding of developers into the Docker platform, easy user management for managers and admins, and seamless authentication for Docker users. Read our blog to learn more about SSO.
Getting Started with the new Authentication Flow
On versions 4.4.2 and above, when users click on “Sign in” from the Docker Dashboard or the Docker Menu, they will be redirected to their default browser.
Once in the browser, you will be prompted to enter your Docker ID. This will take you through the appropriate flow. If your organization has Single Sign-on enabled, you will get redirected to your Identity Provider.
For the standard authentication pattern, users will then be sent to a screen to fill in their username and password. Then click “continue”.
Once you have successfully signed in you will get asked if you want to be taken back to the Docker Dashboard. You can choose to always allow opening Docker to reduce the number of steps in the future.
You’ll be returned to the Docker Dashboard, ready to continue working!
It’s important to note that the command line interface (CLI) login flow and logging into Docker in other tools, such as Visual Studio Code, will continue to work as they do today. You can choose to use a personal access token (PAT) for these flows.
Just update to or download 4.4.2+ to get all the benefits of a simplified sign in experience.
Introduced a fix for CVE-2021-45449
Docker Desktop version 4.3.0 and 4.3.1 have a bug that may log sensitive information (access token or password) on the user’s machine during login. This only affects users if they are on Docker Desktop 4.3.0, 4.3.1 and the user has logged in while on 4.3.0, 4.3.1. Gaining access to this data would require having access to the user’s local files. Additionally, these logs may be included when users upload diagnostics, meaning access tokens and passwords might have been shared with Docker. We have deleted all potentially sensitive diagnostic files from our data storage and will continue to delete diagnostics reported from the affected versions on an ongoing basis. This vulnerability has been fixed in version 4.3.2 or higher. Learn more on our security page.
Chat with us!
We’d love to get your input on our work through user interview sessions. During these live feedback sessions we will often show work-in-progress features or ideas to get your input on, or ask you more about how you use Docker to discover any pain points when working with the product. We use these insights to help prioritize our roadmap and improve the user experience. Each session is typically 30 minutes to an hour. If you would like to take part in one of our user research studies please sign up and we will reach out to you when we have something to research or test.
We’re also working on two of your highest voted items: improving Mac filesystem performance, and implementing Docker Desktop for Linux. For filesystem performance, we’ve been releasing experimental builds using VirtioFS, and we’d love your input on how it works for you: check out the roadmap item for the latest build. For Docker Desktop for Linux, we will have some experimental builds soon, so be sure to follow that roadmap item for news.
What else would you like us to focus on? Have your say by adding a thumbs-up emoji to your highest priorities on the roadmap, or create a new roadmap ticket if your idea isn’t yet there. We can’t wait to hear from you.
DockerCon Live 2022
Join us for DockerCon Live 2022 on Tuesday, May 10. DockerCon Live is a free, one day virtual event that is a unique experience for developers and development teams who are building the next generation of modern applications. If you want to learn about how to go from code to cloud fast and how to solve your development challenges, DockerCon Live 2022 offers engaging live content to help you build, share and run your applications. Register today at https://www.docker.com/dockercon/
The post Seamless Sign-in with Docker Desktop 4.4.2 appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/
Single Sign-on (SSO) for Docker is now live! By enabling SSO, large organizations and enterprises can easily automate the onboarding and management of Docker users at scale. Users can authenticate using their organization’s standard identity provider (IdP). SSO is one of our most widely requested features, so we’re excited to ship this to our Docker Business customers.
Want to enable SSO for your organization? Here are the top things you need to know.
With SSO enabled, users can authenticate using their organization’s standard IdP.
How does SSO work in Docker?
SSO allows users to authenticate to Docker Hub and Docker Desktop using their organization’s standard identity provider (IdP) to access Docker. This will not only make it easier for new users to quickly get started with Docker using their organization-provided email, but it will also help large organizations scale their use of Docker in a more manageable and secure way. Docker currently supports SAML 2.0 and Azure Active Directory IdPs for easy implementation. Once SSO is enabled and configured for your organization, users must sign in to Docker Hub or Docker Desktop to initiate the SSO authentication process.
How is SSO enabled?
SSO is available to organizations with an active Docker Business subscription. This means that customers under the other subscription tiers (e.g., Team) must first upgrade to a Docker Business account. Click here to learn how to upgrade your subscription. Customers with a Docker Business subscription, can visit our documentation for additional information on the enablement process.
Note: When SSO is enabled, logging into Docker via partner products (e.g., VS Code, Jfrog, etc.) will require Personal Access Tokens (PATs).
How are users managed?
Users are managed through organizations in Docker Hub. To configure SSO, each user must already have an existing account in their organization’s IdP. When a user signs into Docker for the first time using their domain email address, they will be automatically added to the organization after the authentication is successful. All users must authenticate using the email domain specified during SSO setup (i.e., company email address). Admins can continue inviting new users to the organization using the Invite Member option in Docker Hub.
How do we convert existing Docker users from non-SSO to SSO?
To convert existing Docker users from a non-SSO account to SSO, admins must verify:
Users have a company email address and account in the IdPUsers have the latest version of Docker Desktop (currently version 4.4.2) installed on their machinesUsers have created a Personal Access Token (PAT) to replace their passwords to allow them to log in through the Docker CLIAll CI/CD pipeline automation systems have replaced their passwords with PATsUsers with email addresses that include the “+” symbol are either added to your IdP or otherwise updated to not include the “+” symbol.
For additional requirements, please refer to our documentation.
What impact can be expected when onboarding users to SSO?
SSO can be enforced for your users once the steps (summarized above and in our documentation) are completed. After SSO is enforced, users can begin signing in using their organization-provided email and password, and then it’s business as usual. Please note that for users logging into Docker directly from the Docker CLI or via partner products (e.g., VS Code, Jfrog, etc.), Personal Access Tokens (PATs) may be required.
For more guidance on how to roll out SSO within your organization, visit our documentation for more information.
Consider making the move today for access to SSO for Docker and other premier features for management and security at scale. Download our latest whitepaper and watch our webinar on-demand to learn more. You can also visit our public roadmap where you can leave feedback on what you want to see next for user management.
DockerCon Live 2022
Join us for DockerCon Live 2022 on Tuesday, May 10. DockerCon Live is a free, one day virtual event that is a unique experience for developers and development teams who are building the next generation of modern applications. If you want to learn about how to go from code to cloud fast and how to solve your development challenges, DockerCon Live 2022 offers engaging live content to help you build, share and run your applications. Register today at https://www.docker.com/dockercon/
The post Introducing SSO for Docker Business appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/
Organizations are increasingly facing new challenges in trying to protect their software supply chain. This has become especially difficult as the workforce has transitioned to a more distributed model with organizations scaling and onboarding more developers on distributed teams. With the number of software supply-chain attacks increasing by 650% in 2021, coordinating all of these developers introduces serious security, management, and visibility challenges for organizations.
We recently hosted a webinar, Securing the Software Supply Chain with Docker Business which is now available on-demand if you missed it. In the webinar, Docker’s CTO Justin Cormack and Customer Success Engineer Nikhi Anand walked through common security challenges, best practices for securing content, how Docker is helping to address the recent Log4j vulnerability, what Docker is actively doing to help keep developer’s work secure, and how Docker Business helps organizations standardize their use of Docker in a way that is scalable and more secure.
Watch a recording of the security webinar on-demand, or keep reading to catch up on what you’ve missed.
Best Practices for Securing Content: Docker Trusted Content
One of the key starting points for securing the supply chain is your developer’s laptops. It’s important that you have insight into which images your developers are using, where they’re coming from, how they’re maintained, and if they conform to current security best practices. Docker trusted content programs like Docker Official Images and the Docker Verified Publisher program provide developers with validation that these images come from trusted sources, reducing the risk of pulling malicious images from impostor repositories.
Docker Official Images are a curated set of Docker repositories hosted on Docker Hub. These images have clear documentation, promote best practices, and are designed for the most common use cases.
The Docker Verified Publisher Program enables Independent Software Vendors (ISVs), development tools vendors, and platform providers to distribute Dockerized content through Docker Hub. The Verified Publisher badge included on the Docker Hub repositories indicates that these repositories are published by Docker partners and are qualified to be included in the developer secure supply chain.
Pulling and running arbitrary public images opens businesses to security risks. Trusted content, including Docker Official Images and the Docker Verified Publisher Images, delivers the reliable building blocks needed for safer application development. These images are maintained, updated on a regular basis, and follow security best practices.
Log4j Vulnerability
During the webinar, Docker CTO, Justin Cormack addressed the recent Log4j 2 vulnerability CVE-2021-44228. The Docker engineering team has been working on several solutions to help our users including:
Shipped several fixes to improve Docker vulnerability scanning so it’s able to pick up Log4j issues in container images. The team is tweaking this as needed.Added a note in the Docker Hub scanning interface that shows images affected by Log4jShipped a feature that shows whether Docker Official Images are vulnerable to Log4j or have been fixed.Put up a page on our website that shows Docker Official Images that contain vulnerable versions and information on the current status updates for Docker Official Images.
Docker’s own infrastructure and Docker Desktop are not affected by the Log4j 2 vulnerability. Docker largely uses Go code to build our applications, not Java. Although we do use some Java applications internally, we have confirmed we are not vulnerable to CVE-2021-44228 and CVE-2021-45046.
What Makes Docker Desktop Secure?
Docker Desktop is an integrated product designed to be a secure desktop system for users. In terms of mitigating security risks, Docker Desktop has a secure lightweight Linux VM that is managed by Docker. As well as setting up this VM with secure defaults, Docker Desktop keeps this VM and all other components up to date for you overtime by applying curl patches or security fixes as required. Docker Desktop also offers a choice of a Microsoft Hyper-V or WSL 2 backend. The Hyper-V backend we ship is fully managed by Docker.
Docker Business offers a control plane with features like Image Access Management and (soon to ship) Registry Access Management so admins can control and manage the images their developers are working with. We’ve been working on additional observability features and we’d love to hear your feedback, please upvote and let us know which features would be most useful for your developers on our roadmap.
Docker vs DIY from a Security Standpoint
One common challenge businesses face to successfully drive innovation is how to ensure developers have the tools they need to simplify their work and enable them to create value while spending minimal time on work that isn’t core to the business. Most business have a strong preference to buy commercial software rather than trying to build their own, some of the key factors in making these decisions are:
Cost of timeOpportunity costTime to valueCost of security risksDoes DIY with open source software make sense for our organization?
If developers are spending time building DIY development projects that aren’t core to the business, it could have a big impact on time to value and return on investment. If you’re considering a DIY with an open source software and Docker Engine approach it’s important to consider whether or not your software teams and engineering resources are prepared and equipped to keep all of the components of a DIY solution updated and all vulnerabilities patched over time.
When you take into account several factories including the cost of time, and time to value, and whether a DIY solution is the best for your organization, the data shows that most organizations will be better off buying commercial software rather than trying to build their own solutions.
Docker SSO is Coming
Some final callouts from the webinar include the announcement that SSO is coming in January 2022 (this month). SSO will enable users to authenticate using their organizations standard identity provider to access Docker, this is one of our most requested features and is included with a Docker Business subscription.
Whitepaper: Build Modern and Secure Applications at Scale with Docker Business
To learn more about some of the topics discussed in the webinar and how Docker Business helps secure the software supply chain with advanced features and capabilities, check out our new Docker Business whitepaper.
Security Q&A
Docker’s CTO Justin Cormack and Customer Success Engineer Nikhi Anand answered Q&A live during the webinar, we’ve captured those webinar questions and answers below.
Is personal data collected with a Docker Desktop Subscription?
We don’t collect any personal data or PII on Docker Desktop. We do collect anonymized data to better understand how people are using our products so we can improve them however all users have the option to opt out of anonymous data collection in their settings. In the future, we will offer a Docker Business feature that allows everyone in an organization to opt out–folks need to opt out on an individual basis for now but this feature is on our roadmap.
Is Docker Business subscription a SaaS offering?
Yes the Docker Business control plane is offered as a service but Docker Desktop itself runs stand-alone on a developer’s workstation. We understand developers like to work offline, so admins can set whether they require team members to login and you can use Docker Desktop disconnected from the business control plane.
How should I handle log4j in my containers?
Rebuilding and updating are your best solutions right now. The most important thing is to update to a fixed version as soon as you can. If you’re using Docker Official Images and deploying as is, look at the release notes on the Docker Official Images site and it’ll tell you if that version has been fixed. We provided scanning tools in the latest release of Docker Desktop that can detect if you have managed to remediate everything effectively so you can use those tools to help make sure that you’ve updated and that you haven’t missed anything.
What are the benefits of updating to the latest version of Docker Desktop?
It is highly recommended to upgrade to the newest version. The longer that you stay on aging software, the greater security risk that you create for yourself. Specifically, old software doesn’t have patches of recently discovered security vulnerabilities, new, frequently-updated software (one of the features of Docker Desktop) always has the latest patches.
Which one is more secure, Hyper-V or WSL 2?
The general consensus right now is that Hyper-V is a little more secure and easier to manage especially with Docker Desktop Hyper-V management and updates. WSL 2 gives you more features and a lot of developers enjoy using WSL 2 on Windows so Docker provides both options. The right option for you and your team really depends on your organization’s needs and requirements.
If we deploy an image to our clients, do the clients need to have a Docker Business subscription to run the image if they have more than 150 employees?
Docker Desktop is licensed based on the person who is using it so yes, your client will need a Docker Business subscription. We’ve had a lot of questions about this type of usage and we know that a lot of folks are using Docker Desktop in this way so we’re interested in learning more about which kind of integrated extensions to Docker Desktop would be helpful for the community. We have a roadmap issue around Desktop Extensions, please share your feedback with us there!
Can you talk a little about container signing and validation and how it’s implemented.
We shipped an integrated project called Notary into Docker Hub years ago. We’re working with Microsoft, Amazon, and other partners on an updated version of this and we’re looking at it as the new container signing framework. We’re planning for this to come out in 2022.
Conclusion and additional resources
Thanks for joining us for our Securing the Software Supply Chain with Docker Business webinar. Below are some additional resources to check out if you want to learn more about Docker Security practices and Docker Business.
The Grace Period for the Docker Subscription Service Agreement Ends Soon – Here’s What You Need to KnowOn-demand webinar: Management & Security at Scale with Docker BusinessWeb page: Considerations for Evaluating Docker Desktop AlternativesWhitepaper: Build Modern and Secure Applications at Scale with Docker BusinessBlog: Secure Software Supply Chain Best Practices
The post Securing the Software Supply Chain with Docker Business appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/
Guest author Ben Hall is the lead technical developer for C# .NET at gov.uk (a United Kingdom public sector information website) and a .NET Foundation foundation member. He worked for nine years as a school teacher, covering programming and computer science. Ben enjoys making complex topics accessible and practical for busy developers.
Deciding Between Docker Desktop and a DIY Solution
At the heart of the Docker experience is Docker Engine. Docker Desktop’s ready-to-use solution for building containerized applications includes Docker Engine and all the other tooling and setup you need to start developing right away.
Developers can create a “DIY” Docker implementation around Docker Engine manually. Some organizations may prefer the flexibility and control of doing it themselves. But opting for a DIY Docker Engine solution requires much more engineering, development, and setup. Docker and its Windows companion, WSL, are relatively complex, so the DIY approach isn’t for everyone.
In this article, we’ll help you decide which approach is right for you and your organization. To illustrate, we’ll draw comparisons between what Docker Desktop offers and a DIY Docker setup on Windows.
Setting Up Docker on Windows
This article on failingfast.io describes the main steps for a manual installation on Windows, which involves creating a WSL 2 distro, setting up a Docker repository, and installing the Docker Engine on the WSL 2 distro additional setup. This process is a bit fragile, so prepare for troubleshooting before you’re up and running. And it’s only a guide to getting started. Most use cases will need further setup, including:
Configuring Docker to start on bootLoggingAccepting connections to Docker daemon from remote hostsConfiguring remote accessFixing IP forwarding problems
Setting up Docker Desktop is a very different experience. You simply download and run the latest Docker Desktop installer — it automatically completes all the work. We’re up and running in a few minutes, ready to deploy containers.
Cutting Edge and Stable
Docker Desktop and the DIY implementation that we linked to share a common foundation on Windows Subsystem for Linux (WSL) 2 that enables developers to run a Linux environment directly on Windows.
WSL 2 significantly improved memory use, code execution, and compatibility. It achieved this through an architectural shift to a full Linux kernel, which supports Linux containers running natively, without emulation.
Working closely with Microsoft and Windows Insider, Docker was quick to adopt this beneficial emerging technology as the primary backend for Docker Desktop. Docker then released a technical preview far in advance of WSL 2 reaching general availability in Windows. Every effort was made also, to maintain feature parity with the previous version that used Hyper-V.
We can add Docker Desktop to our developer tooling, confident that it will continue to support that latest technology while avoiding breaking changes to the experience we are accustomed to.
Software Updates
Docker Desktop manages everything, from setup through to future kernel patches. And because it’s a complete bundle, the automatic software updates will keep all the tools installed on it up-to-date and secure, including the Docker Engine itself. That’s one less machine image to manage in-house!
With a DIY Docker setup, it’s up to you to keep up with all security patches and other updates. A DIY solution will also provide you with plenty of ongoing problems that need solving. So, be sure to multiply those developer hours across a large organization when you are calculating the ROI for Docker Desktop.
Networking
Docker Desktop will automatically propagate configured HTTP/HTTPS proxy settings to Docker to use when pulling containers.
It will also function properly when attached to a VPN. It achieves this by intercepting traffic from containers and injecting it into Windows as if it originated from the Docker application itself.
Pause and Resume
This feature was requested by a user on the public roadmap for Docker Desktop. It’s not the biggest feature ever, but it’s another great reminder that Docker Desktop is under active development. It’s continually being improved in response to user feedback, implemented with monthly releases.
Users can now pause a Docker Desktop session to reduce CPU usage and conserve battery life. When paused, the current state of all your containers is saved in memory and all processes are frozen.
Volume Management
Volumes are the standard approach to persisting any data that Docker containers work with, including files shared between containers. Unlike bind mounts, which work directly with host machine files, volumes are managed by Docker, offering several advantages.
You’ll face two big challenges when working with Docker volumes manually in the Docker CLI:
It can be difficult to identify which container each volume belongs to, so clearing up old volumes can be a slow process.Transferring content in and out of volumes is more convoluted than it really needs to be.
Docker Desktop provides a solution for this by providing a view in the Dashboard to explore volumes. In this view, you can:
Easily identify which volumes are being used See which containers are using a volumeCreate and delete volumesExplore the files and folders in a volume, including file sizesDownload files from volumesSearch and sort by name, date, and size
Kubernetes Integration
Although there are too many features to explore in a single article, we should take a look at the Kubernetes integration in Docker Desktop.
Kubernetes has become a standard for container orchestration, with 83 percent of respondents to the 2020 CNCF Survey reporting that they use it in production.
Granted, we don’t need Kubernetes to get Docker’s benefits in local development, like the isolation from the host system. Plus, we can even use Docker Compose 2.0 to run multiple containers with some nifty networking features. But if you’re working on a project that will deploy to Kubernetes in production, using a similar environment locally is a wise choice.
In the past, a local Kubernetes instance was something else to set up, and the costs in developer time didn’t offer enough benefit to some. This is likely still the case for a DIY Docker solution.
Docker Desktop, in contrast, comes with a standalone Kubernetes server and client for local testing. It’s an uncomplicated, no-configuration, single-node cluster. You can switch to it through the UI, as the image below shows, or in the usual way with kubectl config use-context.
Native Apple Silicon Support
In 2021, a version of Docker Desktop for Mac that could fully leverage the latest M1 chip reached general availability. There are already over 145,000 ARM-based images on Docker Hub. This Apple Silicon version supports multi-platform images, which means you can build and run images for x86 and ARM architectures without complex cross-compilation environments.
This was very well-received because the emulation offered by Rosetta 2, which offers acceptable functionality for many common applications, isn’t sufficient to run containers.
Costs and Scalability
The DIY alternative requires a great deal of engineering time to build and configure, with an ongoing maintenance commitment for updating, patching, and troubleshooting the container environment. Each developer in an organization will carry out most of this work individually every time they work in a fresh environment.
This approach doesn’t scale well! It means developers won’t be spending time on activities directly benefiting the business, like new features. None of us enjoy a sprint review where we have to explain that we didn’t deliver a feature because of problems with or work setting up development environments.
Containerization should help facilitate product delivery. What Docker Desktop sets out to achieve is not new. We have always invested in programming IDEs and other tooling that bundle functionality in a single, user-friendly package to improve productivity.
To help you determine whether Docker Desktop is right for your organization from a cost perspective, Jeremy Castile has some guidance to help you assess the ROI.
Working with Multiple Environments
Developers widely accept that build artifacts must be immutable — the same application, built, must move through QA to production. The next level, if you’d like, is packaging an application and its dependencies together. This helps to further maintain consistency between development, testing, and production environments.
We risk not realizing this benefit if the process is too complicated. Organizations have introduced many great tools and processes to teams, only for these tools to gather dust because the entry bar for the required skills is too high.
This situation is more prominent in QA teams. Many testers are technical, but more typically, they have a particular set of skills geared towards testing. Since QA is one group set to benefit a great deal from consistent testing environments, consider what they are most likely to use.
Introducing Dev Environments
To improve the experience further for these scenarios, Docker Desktop has added a new collaborative development feature, currently in preview, called Dev Environments.
Switching git branches or environments usually requires lots of manual changes to configuration, dependencies, and other environment setup before it’s possible to run the code.
The new feature makes it easy to keep the environment details themselves in source control with the code. With a click of a button, a developer can share their work-in-progress and its dependencies via Docker Hub. This means developers can easily switch to fully functioning instances of each other’s work to, for example, complete a pull request without having to change from their local branch and make all those environment changes.
Get started in Development Environments with the preview documentation.
Conclusion
Bret Fisher, an author who writes about Docker, summed up the need for Docker Desktop: “It’s really a testament to Docker Desktop that there isn’t a comparable tool for local Linux containers on macOS/Windows that solves 80% of what people typically need out of a container runtime locally.”
We’ve explored what Docker Desktop offers and along the way. We’ve also touched on the subjects of cost and ROI, setup and maintenance, scalability, and onboarding. Although some will prefer DIY Docker’s flexibility and control, Docker Desktop requires less setup effort and maintenance, offering a gentler learning curve for everyone from development to QA.
Perhaps the greatest challenge of a DIY solution is from a business value perspective. Developers love discovering how to do these things. So, a developer won’t necessarily track how many hours they spent over a week engaged in maintaining a DIY solution — the business will have no visibility into any productivity loss.If you’re still using a DIY solution for local development with Docker on Windows or macOS, learn more about Docker Desktop and download it to get started.
The post Guest Blog: Deciding Between Docker Desktop and a DIY Solution appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/
Welcome to 2022! Even in normal times, the New Year is a time for looking back and looking forward. And even more after the last couple of years, we know that a lot of people are reassessing their lives and their priorities, and considering moving jobs. If that’s you, we wanted to let you know that Docker is growing fast, and invite you to look at our careers page where we have lots of open positions.
All our positions are remote. Before the pandemic, we had a mixture of office-based and remote employees, but when we were all forced to work from home we found it worked well for us, and we’re sticking with it. (Our VP of Engineering, Jean-Laurent de Morlhon, described more about our remote working journey in a previous blog post).
Where we’re hiring. Even though we’re fully remote, there are only certain countries we can hire in at the moment, based on compatible timezones with our existing teams, and where we’re familiar with local employment law. We plan to expand the list in future, but right now we’re only looking for people in these fifteen countries: Argentina, Brazil, Bulgaria, Canada, France, Germany, Mexico, Netherlands, Poland, Portugal, Romania, Spain, Sweden, UK and USA.
What positions we’re hiring for. As I said, we’re growing fast, and all of our departments are looking for people. Right now we’re looking for
Software developers. We cover a wide software stack in Docker, with everything from the OS, through backend applications, to full stack and UI; we write CLI apps, desktop apps & webs; and use Linux, Windows & Mac.Product managers and product designers. We believe in building the tools our users want, and making them easy to use. To make that happen, every Scrum team contains its own Product Manager and Product Designer.Support engineers and sustaining engineersData engineersSales and Marketing. We have a variety of sales positions from Business Development Reps to Director of Sales Development and a Technical Product Marketing Manager.HR and Finance. These teams support the growth of Docker and there are a variety of roles from HR Coordinator to Sr. Revenue Accountant and more.… with more on the way soon.
What we offer. We want Docker to be a great place to work, and one where people will want to stay for many years. Apart from a competitive salary, here are some of the benefits we offer. (The benefits are broadly the same in each of our countries, but do differ slightly because of local laws).
Freedom & flexibility: fit your work round your life. Now that we’ve fully embraced remote working, it’s important to us that employees get the benefits of that in terms of being able to devise schedules that fit round other parts of their life such as childcare commitments, social clubs, or exercise routines.Stock options. We’re a growing startup, and we want all employees to have a share in the success of the company.Virtual and (when possible!) in-person social events to build connections and have fun. We believe that it’s important to have opportunities to get to know your co-workers on a personal as well as a professional level, even more so in a fully remote company. If you know your colleagues, you will do better work, and have more fun doing it. To that end, we organize virtual and in-person events for teams, for cities or countries, and for the whole company.Home office setup: we want you to be comfortable while you work. If you don’t already have a proper desk, office chair, headset, or similar items, we will supply them.Work From Home allowance equivalent to US$100 after tax per month, to cover the cost of your home internet connection. If you’re using your internet connection for work, we believe we should pay for it.Vacation plan that encourages you to take time off. We don’t believe in burning people out: we want employees to be able to take time off to do the things they enjoy and come back refreshed.Whaleness days: a company-wide day off each month. To improve our work-life balance even further, as a company we shut down for one day each month. This is in addition to your normal vacation allowance. The best thing: unlike normal holidays, you don’t have a huge backlog of email and Slack messages the next day, because everyone else took the day off too!Generous maternity and parental leaveHealth insurance
Where to find out more. If you’re interested in working in an employee-friendly company that’s building the next generation of tools to make developers’ lives easier, then please visit our careers page at docker.com/careers. You can find the current list of vacancies there and apply. Or if you have any questions, you can email us at careers@docker.com. We look forward to hearing from you, and maybe even working with you soon!
DockerCon 2022
Join us for DockerCon 2022 on Tuesday, May 10. DockerCon is a free, one day virtual event that is a unique experience for developers and development teams who are building the next generation of modern applications. If you want to learn about how to go from code to cloud fast and how to solve your development challenges, DockerCon 2022. offers engaging live content to help you build, share and run your applications. Register today at https://www.docker.com/dockercon/
The post Docker is Hiring! appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/
theithollow.com – If you’re struggling to deploy Kubernetes (k8s) clusters, you’re not alone. There are a bunch of different ways to deploy…
Quelle: news.kubernauts.io
mrsauravsahu.medium.com – This is after the announcement of new subscriptions for Docker Desktop, you can read more about it here — https://www.docker.com/blog/updating-product-subscriptions So, in a nutshell, Docker Desktop…
Quelle: news.kubernauts.io
As 2021 comes to an end, it’s time to look back on our top 10 most-read blogs of the year. They cover a range of topics, from updates to our subscription pricing to product announcements to security threats. Here’s a quick summary, starting with the most popular, then ordered by topic.
Updates and extensions to Docker product subscriptions
It should come as no surprise that changes to our product subscriptions — our biggest news of 2021 — was a major driver in blog readership for the year. In fact, three of the top 10 most popular blogs centered on this topic.
In the number one spot is Docker CEO Scott Johnston’s announcement on August 31, Docker is Updating and Expanding Our Product Subscriptions. Scott laid out the four subscription tiers — Docker Personal, Docker Pro, Docker Team, and Docker Business — and provided a detailed breakdown of what users need to know about each, pricing (where applicable), and the why behind the changes.
The fifth and seventh most popular blogs also deal with aspects of the changes to the subscription tiers. Coming in at number five, Steph Rifai zeroed in on the issue of Volume Management in her September 30 blog, Docker Desktop 4.1 Release: Volume Management Now Included with Docker Personal. And at number seven is a September 29 blog by yours truly examining Docker Captain Bret Fisher’s take on possible alternatives to Docker, Looking for a Docker Alternative? Consider This.
Apple Silicon News
Another big driver of eyeballs to our blog was news around developers being able to run Docker Desktop on Apple’s new M1 chip. The second most-read blog of the year is Dieu Cao’s April 15 blog, Released: Docker Desktop for Mac [Apple Silicon], announcing general availability. And coming in at number four is Stephen Turner’s February 17 blog announcing a preview, titled New Docker Desktop Preview for Apple M1 Released.
Log4j 2 Security Vulnerability
The biggest security threat of the year showed up this month, causing our developer community to scramble and work tirelessly these past few days. #HugOps to you. That’s why the third most-read blog of the year focused on fixes for the Log4j 2 vulnerability CVE-2021-44228. Justin Cormack’s blog and updates on the issue, Apache Log4j 2 CVE-2021-44228.
Responding to Your Feedback
The voice of the Docker developer community is hugely important to us. When you speak, we listen. Which is why two of the most-read blogs in 2021 were about improvements to our products in response to your feedback.
Coming in at number six is Chris McLellan’s November 9 blog about the new Pause/Resume feature in Docker Desktop and other changes that make it easier to manage updates: Docker Desktop 4.2 Release: Save Your Battery with Pause / Resume, and Say Goodbye to the Update Pop-up. And at number nine is Dieu Cao’s April 8 blog on changes to how updates work in Docker Desktop, Changing How Updates Work with Docker Desktop 3.3.
Preview: Docker Dev Environments
Our eighth most-read blog of the year is a tech preview that appeared back on June 23. Tech Preview: Docker Dev Environments by Ben De St Paer-Gotch dove into a powerful feature that allows developers to easily share their work-in-progress code for faster, higher-quality collaboration and code reviews.
Hear, Hear for Heredocs!
And the number 10 most-read blog for 2021 details how Docker’s BuildKit tool for building Dockerfiles now supports heredoc syntax, making it easier for developers to do things that were once difficult. The piece, titled Introduction to heredocs in Dockerfiles, was written by Justin Chadell, a member of the Docker community.
So there you have it — the top 10 most popular blogs of 2021. Here’s to an awesome year of growth and expansion in the developer community — and to more must-read blogs — in 2022.
Resources
Download the latest version of Docker Desktop now. See what’s coming up and recommend feature requests in the Docker public roadmap https://github.com/docker/roadmap
DockerCon2022
Join us for DockerCon2022 on Tuesday, May 10. DockerCon is a free, one day virtual event that is a unique experience for developers and development teams who are building the next generation of modern applications. If you want to learn about how to go from code to cloud fast and how to solve your development challenges, DockerCon 2022 offers engaging live content to help you build, share and run your applications. Register today at https://www.docker.com/dockercon/
The post Docker’s Top 10 Most Popular Blogs in 2021 appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/
Docker Captains are select members of the community that are both experts in their field and are passionate about sharing their Docker knowledge with others. “Docker Captains Take 5” is a regular blog series where we get a closer look at our Captains and ask them the same broad set of questions ranging from what their best Docker tip is to whether they prefer cats or dogs (personally, we like whales and turtles over here). Today, we’re interviewing Nana who has been a Docker Captain since 2021. She runs the YouTube channel TechWorld with Nana and is based in Austria.
How/when did you first discover Docker?
In a project I was working on as a junior software developer. I joined a team developing an IoT system where they had selected some of the cool modern technologies and Docker was one of them.
Since Docker was just one of the many technologies we were using in the project, and because of the project deadlines, I was only able to learn just bits and pieces of Docker concepts during the project implementation phase, instead of a proper thorough introduction right at the beginning. So it took me two years to get a good big picture understanding of Docker, where I felt confident I really knew the tool.
From today’s perspective, I wish I had just worked through a 3-4 hour crash course and properly learned it at the beginning.
What is your favorite Docker command?
`docker exec -it container-id`
I use it a lot when playing around with containers, testing and debugging stuff.
What is your top tip for working with Docker that others may not know?
Running docker scan to check for any vulnerabilities in your images. This can give you a lot of confidence to know what kind of images you are producing and deploying.
What’s the coolest Docker demo you have done/seen ?
For my DevOps bootcamp I built a scenario, where:
I took a simple Nodejs application, dockerized it using a Dockerfile, added docker-compose file to run a database service and the application with, then configured a fully-automated CI/CD pipeline thatbuilt the image from this Dockerfile, pushed it to a private Docker registry, then automatically incremented the docker image version in a docker-compose file, copied it to an EC2 server, with Docker already installed on and started the application and its database by running docker-compose up on the ec2 server and finally validate that the application was deployed and the endpoint was accessible.
It was really fun to see how Docker can be integrated so well with all these different technologies
