September 2017 - Seite 43 von 195 - Cloud Computing Köln

Microsoft SQL Server 2017 is now available for the first time on multiple platforms: Windows, Linux and Docker. Your databases can be in containers with no lengthy setup and no prerequisites, and using Docker Enterprise Edition (EE) to modernize your database delivery. The speed and efficiency benefits of Docker and containerizing apps that IT Pros and developers have been enjoying for years are now available to DBAs.

Try the Docker SQL Server lab now and see how database containers start in seconds, and how you can package your own schemas as Docker images.

If you’ve ever sat through a SQL Server install, you know why this is a big deal: SQL Server takes a while to set up, and running multiple independent SQL Server instances on the same host is not simple. This complicates maintaining dev, test and CI/CD systems where tests and experiments might break the SQL Server instance.
With SQL Server in Docker containers, all that changes. Getting SQL Server is as simple as running `docker image pull`, and you can start as many instances on a host as you want, each of them fresh and clean, and tear them back down when you’re done.
Database engines are just like any other server-side application: they run in a process that uses CPU and memory, they store state to disk, and they make services available to clients over the network. That all works the same in containers, with the added benefit that you can limit resources, manage state with volume plugins and restrict network access.
Many Docker customers are already running highly-available production databases in containers, using technologies like Postgres. Now the portability, security and efficiency you get with Docker EE is available to SQL Server DBAs.

Modernize your database delivery with Docker

Traditional database delivery is difficult to fit into a modern CI/CD pipeline, but Docker makes it easy. You use Microsoft’s SQL Server Docker image and package your own schema on top, using an automated process. Anyone can run any version of the database schema, just by starting a container – they don’t even need to have SQL Server installed on their machine.
This is the database delivery workflow with Docker:

DBA pushes schema changes to source control
CI process packages the schema into a Docker image based on Microsoft-published SQL Server base images
CI process runs test suites using disposable database containers created from the new image
CD process upgrades the persistent database container in the test environment to the new image
CD process runs a database container to upgrade the production database, applying diff scripts to align the schema to the new image

The whole process of packaging, testing, distributing and upgrading databases can be automated with Docker. You run database containers in development and test environments which are fast, isolated, and have identical schema versions. You can continue using your existing production database, but use the tested Docker image to deploy updates to production.
Support and availability
Docker Enterprise Edition is a supported platform for running SQL Server in Linux in containers in production. SQL Server for Linux is a certified container image which means you have support from Microsoft and Docker to resolve any issues.
On Windows Server and Windows 10 you can run SQL Server Express in containers with Docker, to modernize your database delivery process for existing SQL Server deployments, without changing your production infrastructure.
The new SQL containers will be available for download in Docker Store in October – but you can start testing with the pre-GA containers in Store today. Already there have been over 1 million downloads from Docker Hub of the SQL Server preview for Linux containers.

Yes you can run databases in containers – #SQLServer on #Docker EEClick To Tweet

To learn more about Docker solutions for IT:

Try out the SQL Server Docker lab and run your own database containers
Visit IT Starts with Docker and sign up for ongoing alerts
Learn more about Docker Enterprise Edition and start a hosted trial
Sign up for upcoming webinars

The post Yes to databases in containers – Microsoft SQL Server available on Docker Store appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

26. September 2017

da Agency

Exciting new things for Docker with Windows Server 17.09

What a difference a year makes… last September, Microsoft and Docker launched Docker Enterprise Edition (EE), a Containers-as-a-Service platform for IT that manages and secures diverse applications across disparate infrastructures, for Windows Server 2016. Since then we’ve continued to work together and Windows Server 1709 contains several enhancements for Docker customers.
Docker Enterprise Edition Preview
To experiment with the new Docker and Windows features, a preview build of Docker is required. Here’s how to install it on Windows Server 1709 (this will also work on Insider builds):
Install-Module DockerProvider
Install-Package Docker -ProviderName DockerProvider -RequiredVersion preview
To run Docker Windows containers in production on any Windows Server version, please stick to Docker EE 17.06.
Docker Linux Containers on Windows
A key focus of Windows Server version 1709 is support for Linux containers on Windows. We’ve already blogged about how we’re supporting Linux containers on Windows with the LinuxKit project.
To try Linux Containers on Windows Server 1709, install the preview Docker package and enable the feature. The preview Docker EE package includes a full LinuxKit system (all 13MB of it) for use when running Docker Linux containers.
[Environment]::SetEnvironmentVariable(“LCOW_SUPPORTED”, “1”, “Machine”)
Restart-Service Docker
To disable, just remove the environment variable:
[Environment]::SetEnvironmentVariable(“LCOW_SUPPORTED”, $null, “Machine”)
Restart-Service Docker
Docker Linux containers on Windows is in preview, with ongoing joint development by Microsoft and Docker. Linux Containers is also available on Windows 10 version 1709 (“Creators Update 2”). To try it out, install the special Docker for Windows preview available here.
Docker ingress mode service publishing on Windows
Parity with Linux service publishing options has been highly requested by Windows customers. Adding support for service publishing using ingress mode in Windows Server 1709 enables use of Docker’s routing mesh, allowing external endpoints to access a service via any node in the swarm regardless of which nodes are running tasks for the service.
These networking improvements also unlock VIP-based service discovery when using overlay networks so that Windows users are not limited to DNS Round Robin.
Named pipes in Windows containers
A common and powerful Docker pattern is to run Docker containers that use the Docker API of the host that the container is running on, for example to start more Docker containers or to visualize the containers, networks and volumes on the Docker host. This pattern lets you ship, in a container, software that manages or visualizes what’s going on with Docker. This is great for building software like Docker Universal Control Plane.
Running Docker on Linux, the Docker API is usually hosted on Unix domain socket, and since these are in the filesystem namespace, sockets can be bind-mounted easily into containers. On Windows, the Docker API is available on a named pipe. Previously, named pipes where not bind-mountable into Docker Windows containers, but starting with Windows 10 and Windows Server 1709, named pipes can now bind-mounted.
Jenkins CI is a neat way to demonstrate this. With Docker and Windows Server 1709, you can now:

Run Jenkins in a Docker Windows containers (no more hand-installing and maintaining Java, Git and Jenkins on CI machines)
Have that Jenkins container build Docker images and run Docker CI/CD jobs on the same host

I’ve built a Jenkins sample image (Windows Server 1709 required) that uses the new named-pipe mounting feature. To run it, simple start a container, grab the initial password and visit port 8080. You don’t have to setup any Jenkins plugins or extra users:
> docker run -d -p 8080:8080 -v .pipedocker_engine:.pipedocker_engine friism/jenkins
3c90fdf4ff3f5b371de451862e02f2b7e16be4311903649b3fc8ec9e566774ed
> docker exec 3c cmd /c type c:.jenkinssecretsinitialAdminPassword
<password>
Now create a simple freestyle project and use the “Windows Batch Command” build step. We’ll build my fork of the Jenkins Docker project itself:
git clone –depth 1 –single-branch –branch add-windows-dockerfile https://github.com/friism/docker-3 %BUILD_NUMBER%
cd %BUILD_NUMBER%
docker build -f Dockerfile-windows -t jenkins-%BUILD_NUMBER% .
cd ..
rd /s /q %BUILD_NUMBER%
Hit “Build Now” and see Jenkins (running in a container) start to build a CI job to build a container image on the very host it’s running on!
Smaller Windows base images
When Docker and Microsoft launched Windows containers last year, some people noticed that Windows container base images are not as small as typical Linux ones. Microsoft has worked very hard to winnow down the base images, and with 1709, the Nanoserver download is now about 70MB (200MB expanded on the filesystem).
One of the things that’s gone from the Nanoserver Docker image is PowerShell. This can present some challenges when authoring Dockerfiles, but multi-stage builds make it fairly easy to do all the build and component assembly in a Windows Server Core image, and then move just the results into a nanoserver image. Here’s an example showing how to build a minimal Docker image containing just the Docker CLI:
# escape=`
FROM microsoft/windowsservercore as builder
SHELL [“powershell”, “-Command”, “$ErrorActionPreference = ‘Stop'; $ProgressPreference = ‘SilentlyContinue';”]
RUN Invoke-WebRequest -Uri https://download.docker.com/win/static/test/x86_64/docker-17.09.0-ce-rc1.zip -OutFile ‘docker.zip’
RUN Expand-Archive -Path docker.zip -DestinationPath .

FROM microsoft/nanoserver
COPY –from=builder [“dockerdocker.exe”, “C:Program Filesdockerdocker.exe”]
RUN setx PATH “%PATH%;C:Program Filesdocker”
ENTRYPOINT [“docker”]
You now get the best of both worlds: Easy-to-use, full-featured build environment and ultra-small and minimal runtime images that deploy and start quickly, and have minimal exploit surface area. Another good example of this pattern in action are the .NET Core base images maintained by the Microsoft .NET team.
Summary
It’s hard to believe that Docker Windows containers GA’d on Windows Server 2016 and Windows 10 just one year ago. In those 12 months, we’ve seen lots of adoption by the Docker community and lots of uptake with customers and partners. The latest release only adds more functionality to smooth the user experience and brings Windows overlay networking up to par with Linux, with smaller container images and with support for bind-mounting named pipes into containers.
To learn more about Docker solutions for IT:

Learn more about Docker for Windows
Visit IT Starts with Docker and sign up for ongoing alerts
Learn more about Docker Enterprise Edition
Sign up for upcoming webinars

Exciting new things for #Docker with @Windows Server 17.09 Click To Tweet

The post Exciting new things for Docker with Windows Server 17.09 appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

26. September 2017

da Agency

North Korea Says Trump's Tweet Is A Declaration Of War. Twitter Won't Say If It Violates Its Rules.

Getty Images / John Paczkowski

On Monday morning North Korea's foreign minister told journalists gathered near the United Nations that president Trump's recent tweet about North Korea were a declaration of war against his country. Trump's “they won't be around much longer!” tweet and North Korea's interpretation of it are the latest in a series of escalations between the two powers that have set the international community on high alert. Since Trump made the remark on Twitter, today's comments from North Korea also raise the question: does a threat that leads to a declaration of war violate the company's opaque rules for conduct and its prohibitions against harassment and incitement?

Twitter appears unwilling to weigh in. Asked for comment on Trump's September 23rd tweet — specifically if it violates the company's terms of service — a Twitter spokesperson told BuzzFeed News it “does not comment on individual accounts for privacy and security reasons.”

Twitter's silence comes as little surprise — the company's decision not to comment on individual accounts for privacy reasons (even when the account is held by the President of the United States to conduct government business) is a long-held policy designed to shield the company from accountability. And while Trump has continually tested the limits of Twitter's rules throughout his candidacy and presidency, the latest escalation, this particular tweet is clearly uncharted territory for the social network.

Following a strict interpretation of Twitter's rules, Trump's recent tweet — a clear threat toward North Korea's foreign minister — is likely a violation of Twitter's rules, which state that “you may not incite or engage in the targeted abuse or harassment of others” and defines abusive incitement as:

If a primary purpose of the reported account is to harass or send abusive messages to others;

If the reported behavior is one-sided or includes threats;

If the reported account is inciting others to harass another account; and

If the reported account is sending harassing messages to an account from multiple accounts.

Historically, Twitter's interpretation and enforcement of its rules have been inconsistent. And though Twitter told Slate late last year that its policies apply to all its users, the company has been reluctant to weigh in on Trump's conduct on its platform. In December 2016 the company declined to comment when Trump used his Twitter account to lambaste Chuck Jones, an Indiana union organizer who criticized him; The Washington Post reported that Jones was inundated with threatening phone calls as a result. And the company took no action this summer when Trump tweeted a meme that showed him as a wrestler body slamming the CNN logo — an instance that some interpreted as a threat against at journalists.

For tweets like these, the New York Times has dubbed Trump the “Cyberbully in Chief” and Twitter CEO Jack Dorsey has described his feelings about Trump's use of Twitter as “”complicated.” But Monday's statements threaten to raise the stakes for the social network and present a series of difficult policy questions as to how it enforces its rules with the commander in chief. Among them: does the President of the United States merit a Twitter rules exemption? Is a tweet interpreted as a declaration of war a violation of the company's terms of service?

This is — again — uncharted territory for the social network. But while Twitter opts for silence, others, including North Korea are speaking up. Outside the U.N. Minister Ho told reporters that Trump's tweet would not go unanswered.

Quelle: <a href="North Korea Says Trump's Tweet Is A Declaration Of War. Twitter Won't Say If It Violates Its Rules.“>BuzzFeed