text:
Walter Cronkite, Barack Obama, Oprah Winfrey, and the Occupation of Iraq
I used to listen to Cronkite (every night) and Winfrey comes up more than a day late and a dollar short.
Marty Kaplan says that Oprah is to Iraq as Walter was to Vietnam:
. . . I watched Oprah Winfrey stump for Barack Obama this weekend . . . It's about reassuring the overwhelming majority of Americans who oppose the war in Iraq that they are, in fact, an overwhelming majority. It's also about giving courage or cover to every Democratic member of Congress . . . .
How do people know what other people think? The sad truth is that it doesn't come from talking to one another; it comes from the media.
. . . . no journalist can today occupy the place that Walter Cronkite did when, at the end of a CBS documentary about the 1968 Tet offensive, he said the U.S. was in a stalemate in Vietnam and should get out . . . . Bill Moyers, Keith Olbermann, Jon Stewart and Stephen Colbert actually do tell the truth, and they mercilessly deconstruct the biases of "fair and balanced" faux news and fatuous "narrative" narratives, but their audience sizes limit their impact, and their matter is more than matched by Republican media anti-matter.
But Oprah -- well, in an age that has thoroughly blurred the boundary between news and entertainment, Oprah may actually be the twenty-first century's de facto national anchor. She really does channel -- and change -- Middle America.
. . . . Oprah's audience will take from this the message that their own opposition to the war isn't a betrayal of the troops, as the Republicans claim; isn't giving comfort to the terrorists, as the administration asserts; isn't moral cowardice, as the Right's bile-spewing whiner intelligentsia insists. And maybe the message that current and aspiring members of Congress will take from Oprah's unembarrassed anti-war message is that it's not political suicide to stand with the decisive majority of the American people, that being called bad names by your opponents will not kill you. . . .
If Oprah can feel it and think it and say it, then you can feel it and think it and say it. What's not in question is the message to Democratic politicians, especially incumbents, still weaseling on Iraq: If you've lost Oprah, you've lost Middle America.
I concede that Kaplan makes some strong and eloquent points here. No Doubt. But let me review the historical antecedents involved here.
In the wake of his visit to Vietnam during the Tet Offensive, CBS News anchor Walter Cronkite concluded his 27-Feb-1968 broadcast with his famous and unusually personal Report from Vietnam:
. . . we'd like to sum up our findings in Vietnam, an analysis that must be speculative, personal, subjective.
Who won and who lost in the great Tet offensive against the cities? I'm not sure. The Vietcong did not win by a knockout, but neither did we. The referees of history may make it a draw. Another standoff may be coming in the big battles expected south of the Demilitarized Zone. Khesanh could well fall, with a terrible loss in American lives, prestige and morale, and this is a tragedy of our stubbornness there . . it is doubtful that the American forces can be defeated across the breadth of the DMZ with any substantial loss of ground. Another standoff. On the political front, past performance gives no confidence that the Vietnamese government can cope with its problems, now compounded by the attack on the cities. It may not fall, it may hold on, but it probably won't show the dynamic qualities demanded of this young nation. Another standoff.
We have been too often disappointed by the optimism of the American leaders, both in Vietnam and Washington, to have faith any longer in the silver linings they find in the darkest clouds . . . it seems now more certain than ever that the bloody experience of Vietnam is to end in a stalemate. . . .
To say that we are closer to victory today is to believe, in the face of the evidence, the optimists who have been wrong in the past. To suggest we are on the edge of defeat is to yield to unreasonable pessimism. To say that we are mired in stalemate seems the only realistic, yet unsatisfactory, conclusion. . . . But it is increasingly clear to this reporter that the only rational way out then will be to negotiate, not as victors, but as an honorable people who lived up to their pledge to defend democracy, and did the best they could.
Cronkite had been either neutral or pro-war before he was against it. But with this single and unique (for him) editorial, this peerless broadcast journalist opened an immense credibility cap for Lyndon Baines Johnson who immediately reacted by turning to his aides and saying,
If I've lost Cronkite, I've lost Middle America.
LBJ knew at that moment he would have to change course. A month later Johnson declined to run for reelection and announced that he was seeking a way out of the war. David Halberstam wrote that this "was the first time in American history a war had been declared over by an anchorman."
Against this Cronkite standard, how does Oprah's out-of-the-closet anti-war endorsement of Barack Obama measure up?
Oprah's conversion is late. Winfrey was pro-Iraq invasion and occupation before she was against it. She has arrived late to an anti-war position. As a matter of fact, coming out of the closet last Saturday, she is 62 months later than then State Senator Obama (Oct'02), who was publicly against the invasion before it was launched. Compare Cronkite and Winfrey statements relative to LBJ's and GWB's 2nd-term elections (1968 and 2004): Cronkite's editorial was delivered 8+ months before LBJ's re-election and Winfrey's coming-out followed GWB's re-election by 37½. Assuming Winfrey's opinion-molding influence was on a par with Cronkite's, how much would have her more timely conversion saved our country and the world in terms of unnecessary blood, treasure and delay in national redemption?
Cronkite and Winfrey had/have different audiences. In 1964, Cronkite was the TV anchor of record. He was peerless in terms of delivering an objective and authoritative version of the day's news, sort of what we are supposedly treated to by Jim Lehrer and the PBS News Hour currently. His audience tuned in because they were stakeholders in the consequences (economic and political) of the current events of the day. As such, they were voters. Winfrey's audience, I would wager, are significantly less likely to be voters. Cronkite's viewers were policy wonks; Winfrey's day-time listeners are a different kind of junky, pursuing a little encouragement and information about weight loss, stress, fashion, etc.
Cronkite addressed the fortunes of a war effort and his remarks had consequences for a sitting (and conscientious) President; Winfrey is primarily addressing the fortunes of a favored presidential candidate who might force an early end of our current Iraq war occupation.
Don't get me wrong. I am glad that Oprah Winfrey is endorsing my favored candidate. She brings incredible heat to any table she draws her chair up to, as the You-Tubes from the past weekend attest. I have to cop to having had her pull me to my feet in front of my C-Span with her Miss Jane Pittman routine.
Winfrey reflects on the Ernest Gaines novel which later became an iconic, Emmy Award-winning movie, "The Autobiography of Miss Jane Pittman," (a story of a woman born into slavery who lived to see the day when she could drink in the "Whites Only" fountain in a segregated town). Winfrey recalled actress Cicely Tyson's performance:
When Miss Jane Pittman would encounter young people throughout that film, she would ask, 'Are you the one?' I remember her standing in the doorway, her body bent, frail, old, holding the baby in her arms, saying, 'Are you the one, Jimmy? Are you the one?'
I believe in '08, I have found the answer to this question. It is the same question that our nation is asking: Are you the one? Are you the one?
I am here to tell you, Iowa, he is the one.
Deep down, I get Oprah Winfrey. Neither of us are single-issue voters. If we were only voting for peace, we would be pushing for Senator Gravel, Representative Kucinich or the pandering governor from New Mexico. Both of us see more is at stake in the 2008 election than filling in the latrine of mass graves Bush has left us Americans in Mesopotamia. If Oprah can prevent Hillary Clinton from playing Richard Nixon to George Bush's LBJ, more power to her. She may have missed or fallen short of her Walter Cronkite moment. But Oprah Winfrey is right on the one key point.
posted by Vigilante at 12/10/2007 11:51:00 PM 15 comments


What a day for it.
Ok so it was only a quick spin on the Berger Van,but it was such a nice crisp sunny day out.
Last edited by Japcati; 2nd February 2019 at 08:00 PM.
Re: What a day for it.
Was a nice spin out through Malahide,along the coast road into Portmarnock,then on to Sutton Cross,up over Howth Head,down into Howth Harbour,and stopping off at Dollymount Beach and the Happy Out Cafe for a cuppa coffee.
Cold but lovely day none the less.


Ideal for home decor - these hand-embroidered elephants make great mobile hangings. The colorful beads, pom poms and tassel adds a unique beauty and feeling.
This design was inspired from a close-knit relationships in elephants.
This handmade item is exactly as shown in the picture.
A lot of care, work, and love is put into making this item. For sure, you will feel the uniqueness and comfort when you hold this.


I want to say that I'm very much in favour of the work Kevin is doing. I think it's great to look into improving humans and giving us some robot form.
Thank you for your support. I'm sure there are lots of people who would like to have implants so they can understand different things and have different experiences.
Previous What does the word bionic actually mean and how would a bionic object be incorporated into the body?
Next Will aftershave relieve the pain of spondylitis?


Picket Fences (CBS, 9-10 p.m.): This is the last chance for fans to catch the critically acclaimed but sometimes bizarre antics of those folks in Rome, Wis. Though the finale of the canceled series has already aired, CBS recently dusted off several episodes that were already in the can; in this last first-run episode, a meaningless tragedy has Jimmy pondering the transience of life.
Peter Jennings Reporting (ABC, 10-11 p.m.): "Never Say Die: How the Tobacco Companies Keep on Winning" focuses on the astounding legal successes of the tobacco companies. The program features original research on the use of tobacco by children and an interview with presidential hopeful Bob Dole. The report probes the question, "How can the tobacco companies continue to not just survive, but prosper, when so many of their customers do not," executive producer Thomas Yellin told TV Guide.
World of Discovery (ABC, 8-9 p.m.): James Brolin hosts "Last Charge of the Rhino," a sobering look at efforts to save the black rhinoceros, which has been hunted to the brink of extinction by its only enemy: man. In a sad irony, the rhino's main form of defense, its horn, is what makes it valuable to poachers, who have decimated about 95 percent of the black rhino population since 1970. Efforts to save these gentle creatures include moving them to Australia and dehorning them - rendering them worthless to poachers, but denuding them of their main means of protection.
Citizens '96 (PBS, 11:30 p.m.-12:30 a.m.): This election-year program takes a look at the political catch-phrase "family values." The documentary interviews citizens from Rockford, Ill. (which mirrors national statistics on racial population, income, and unemployment), on the role of family today. In an effort to be all-encompassing, the show skims the surface of difficult issues, but one fact emerges: Few of those interviewed welcome government intervention in their family life.
South Africa legalizes sales of rhino horn: Will this help save rhinos?


text:
Home > Resources > Product News > Content Piece
Shimadzu Partners with Front Range Biosciences to Establish a Hemp Science Center of Excellence
Original story from Shimadzu
Want a FREE PDF version of This Product News?
Complete the form below and we will email you a PDF version of " Shimadzu Partners with Front Range Biosciences to Establish a Hemp Science Center of Excellence"
Shimadzu Scientific Instruments (SSI) and Front Range Biosciences (FRB) have announced a partnership to establish a Hemp Science Center of Excellence. Through this collaborative research and education agreement, SSI will provide instrumentation to support FRB's new analytical laboratory for hemp research and development.
The FRB Hemp Science Center of Excellence will focus on genetics, biobanking, breeding, and analysis utilizing Shimadzu HPLC/UHPLC, LC-MS/MS, GC-MS/MS, and MALDI-TOF MS instruments. Scientists at the new center will conduct chemical and genetic analytical research to support the development of new hemp varieties for the production of cannabinoids, terpenoids, and other compounds for medical and wellness applications; lipid, wax, and protein ingredients for food and cosmetics applications; and fiber for industrial applications.
Located at FRB's new 39,000-square-foot headquarters in Boulder, Colorado, the center will also foster collaborations with researchers from private and public sectors, including academic, nonprofit, and governmental agencies. FRB will work with SSI to expand its existing academic collaborations with renowned institutions such as Colorado University–Boulder, Colorado University–Pueblo, University of California–Davis, University of Vermont, University of Wisconsin and Cornell University, allowing investigators at other institutions to apply for grants to support students, postdoctoral candidates and other researchers at the Center of Excellence. FRB and Shimadzu will work together to evaluate and accept applications for visiting research positions.
"Front Range Biosciences is honored to partner with the world-class team at Shimadzu. Combining their innovative and proven cannabis and hemp analytical instrumentation solutions with our next-generation breeding program, we will be well-positioned to continue advancing the industry with data-driven science so we can harness the incredible potential of this versatile plant for therapeutic, wellness, nutrition, and industrial applications," said Dr. Jonathan Vaught, CEO, and co-founder of FRB. "We are confident that with Shimadzu's cutting-edge technology, we will be able to drive forward-thinking solutions in this growing industry to better serve farmers, producers, and consumers."
"Front Range Biosciences is a leader in plant genetics, and we are excited to support their work to advance hemp analysis and breeding science," said Bob Clifford, Ph.D., general manager of marketing, Shimadzu Scientific Instruments. "The new technology and methods developed at the Center of Excellence will accelerate the growth of this burgeoning industry by increasing and improving hemp-derived products, not only for oils and fiber but also for health and wellness applications."
Shimadzu's hemp testing solutions cover a broad range of applications, from accurate potency testing and terpene profiling to contaminant testing for pesticides, residual solvents, heavy metals, and mycotoxins/aflatoxins.
This article has been republished from material provided by Shimadzu. Note: material may have been edited for length and content. For further information, please contact the cited source.

redpajama_set_name: RedPajamaCommonCrawl


text:
Q: Why can I extend this class with a different name? in prestashop 1.6 (but I guess it's just a desing pattern), there a main class interface defined like this:
abstract class ObjectModelCore implements Core_Foundation_Database_EntityInterface

But then, when you want create an ObjectModel, you do like this:
class CustombannersBannerbox extends ObjectModel

Well, I cannot understand why. I mean, if the ObjectModelCore is called, well, ObjectModelCore, why can I extend it calling it ObjectModel?

redpajama_set_name: RedPajamaStackExchange


Fill out a request form and one of our advisors will contact you to discuss your requirements, find an appropriate solution and then send you a quote for your customized configuration. We absolutely do NOT sell your contact info. It is ONLY used to communicate with you about our products.


Karndean Luxury Vinyl Flooring Da Vinci Collection - Huge savings!
Explore Karndean Da Vinci Collection Luxury Vinyl Tile and Plank Flooring styles!
Buy Karndean Da Vinci Collection Luxury Vinyl Tile & Plank Flooring Today and Save!
Bringing the natural beauty and intricate textures of real stone and woods indoors, the Karndean Da Vinci stone tile designs take inspiration from weathered steel, natural stone, and woven fabric and offer a fresh palette of colors to suit any home. Karndean Da Vinci stone tiles are designed to offer a sophisticated and understated look, the four natural stone designs feature the realistic grain and fossilization of limestone. The Karndean Da Vinci Collection is perfect for both residential and commercial interiors, with the creamy tone of Dune and Bluff to the darker, grainer Sable and Drift. Popular for its narrow wood effect planks, deep bevel, and smooth finish, the Da Vinci wood collection features twelve trendy, new 'modern rustic' designs. The twelve new designs are split into two groups – including modern limed planks and classic oak looks, whilst the second group features burnt and smoked designs alongside worn, aged driftwood looks.


Warner Bros. Entertainment has announced today two new animated projects based on the Batman Unlimited and DC Super Friends children's toylines, featuring characters from the DC Comics universe.
Batman Unlimited will have two direct-to-video releases. The first one is titled Animal Instincts, and will pit re-designed versions of Batman, Nightwing, Red Robin, Flash, and Green Arrow against the Penguin's army of robotic animals. This film will be released on May 12th, and will be distributed in DVD, Blu-Ray, and Digital HD releases. A sequel will also be released sometime later in 2015.
In addition, Batman Unlimited has an order of 22 animated shorts that last two-minutes each. These shorts, as well as any additional content available, can be accessed digitally for free and through an app for young viewers.
The Fisher-Price Imaginext toyline DC Super Friends will also be releasing new animated content in the form of 15 three-minute animated shorts. These will also be released through a digital app. The Justice League roster includes Batman, Superman, Wonder Woman, Flash, Cyborg, Aquaman, and Green Lantern Hal Jordan. Some of the characters use costumes inspired by DC's Nu52 reboot.
These projects continue WB and DC's efforts to bring animation through different venues beyond television. The use of direct-to-video content is not new, as both companies have an animated movie line that adapts several adult comic book stories. Digital content also has a precedent with the previous announcement of the Vixen mini-series for CW Seed that takes place in-continuity with hit-shows Arrow and The Flash.
What do you think of these releases? Let us know by commenting below!


HOpe you get better. Shame you can't vote online for the pictures.
That horrible cold/flu thing is all over Australia. Ellen's kinder saw 9 kids missing kinder on Tuesday, Phaedon's kinder had 8 missing today. I copped it too this week.I sure hope you get better soon.
hope you feel better soon. take care..
Yech!! Hope you are on the mend Danielle...my DS is down with it too...not good.
Hope you're doing okay. My boys had the dreadful flu - knocked them out for 9 days! Hang in there!
Hope your feeling better it has taken about 4 weeks for me to get over the last bad flu and I am still coughing.


Orchestra music led by the renowned Brass brand Valaisan Constellation, Vatel Switzerland's General Manager, Mr. Yves Defalque, Academic Director Mr. Pierre-Antoine Dubuis, and this year's Event Ambassador Mr. Jean Troillet, handed the new Bachelor and MBA graduates their degrees. In addition, prizes were awarded to the best theoretical students, the best practical students, those who had made the best group projects, and the best Vatel Ambassadors of the year.
After the ceremony, the festivities continued onward at the Hotel Vatel around a beautiful buffet prepared by Vatel Switzerland's Chef, Thierry Laurier. The variety of cuisine was inspired by five countries that Mr. Jean Troillet had traveled to which included: Russia, Japan, Switzerland, Peru and Pakistan. Champagne aperitif, DJ, photo booth, everything was on point for the accomplishment into the 35000 alumnis worldwide network. Find them soon on our page sucessful Vatelians !


A short and sweet psalm.
Nelson, Inc. Used by permission.
Some of my thoughts... One of the interesting things about this psalm is how serene, but also confident David is. I mean, how often do we as Christians go and say to God, "Lord, my eyes heart isn't proud. My eyes aren't lifted up." But isn't that just what Jesus exemplified, and even Himself admitted when he said, "for I am gentle and lowly in heart." Just kind of makes me wonder if it's possible for me to come to a place like that. He did say "all things are possible to those who believe," right? Aren't we supposed to be transformed into His image? I think maybe I am afraid of being prideful, and to say "I'm humble" immediately disqualifies me. Anyone else ever feel like that? Is it Scriptural? I don't know. There seems to be several verses that would hold up in court for just the opposite.
Hope you like the song.


Franklin Matters: FHS' Haba among HockomockSports.com's "Baseball: Ten Players to Watch for 2019"
FHS' Haba among HockomockSports.com's "Baseball: Ten Players to Watch for 2019"
HockomockSports.com has published their "Baseball: Ten Players to Watch for 2019" which features one player from FHS.
"The Franklin Panthers have had a lot of success over the past two seasons, and one constant in that time period has been shortstop Alex Haba. Haba burst onto the scene as a sure-handed shortstop during his sophomore year and has been one of the best defensive players at any positions since then.
At one of the most important spots on the field, Haba routinely makes difficult plays look easy. And over the past two years, he's really improved on the offensive end. Last season, Haba batted .328 during the regular season with 22 hits, 12 RBI and 15 runs scored. Haba will be a leader for the Panthers this year, both on and off the field, and could be one of the best overall players in the league."


text:
Janina Pescinski
Position:United Nations University Institute on Globalization, Culture and Mobility, Spain
Fellowship:2012 Amsterdam Fellowship
Janina Pescinski is a Junior Research Fellow at the United Nations University Institute on Globalization, Culture and Mobility in Barcelona. Her current research takes a human rights approach to migration, with a particular focus on the Mediterranean, and she has also worked on questions of female agency and humanitarian assistance to migrants. Previously, Janina worked for Amnesty International in Paris conducting research on West Africa, and as a development associate at the Women and Health Alliance International. She earned her BA in Cultural Anthropology at Rutgers University and MA in Human Rights at Sciences Po Paris. Janina is a Humanity in Action Senior Fellow (The Netherlands 2012).
Humanity in Action
41 Flatbush Avenue, Suite 1
Email: usa@humanityinaction.org


Can Titanium Rings Be Resized?
A lot of Titanium ring suppliers give a warning about taking care with getting the size right as it can't be altered in the future - this isn't strictly the case as it all depends on different factors.
· Is it diamond set?
· Does it have a precious metal inlay?
· Does it need to go up or down in size.
Grade 2 commercially pure Titanium is fairly ductile and will stretch and compress quite readily. If it has a precious metal inlay set into the outside it is probably better to take a skim out of the bore to make it bigger - stretching will normally cause the inlay to split. The amount of increase could be up to about two sizes.
Compressing a ring with an inlay is usually ok for about one size. Compressing plain rings depends on the outside pattern. If it is patterned then the amount of force required to compress it will undoubtedly cause too much damage to repair the outer surface economically and so should be avoided.


vectis - Page 9- BLOOD FOR THE BARON!!!
Nice stuff jim. More ATT mockups.
Notice the SAS is tippexed. Seems all the opened stuff was opened for a reason, and not played with.
Yeah vectis ballsed up with this stuff...luckily for us!
topson wrote: Ok, here is the Deep Six. It is hand painted and has a lot of great details. I love this one and really wish Palitoy had mass produced it.
The figure has dark brown hair.
THANK YOU SO MUCH FOR SHARING THIS!!! Absolutely brilliant!
Sorry to be cheeky, but please could we see some side photos too? I can make out some red paint but can't tell if it's detail or a Q logo.
topson wrote: Lastly, there is a Black Major that has a cruder skull and cross bones logo on his chest than the one in the Blood archives and the stripes on his arms are crisper/more distinct than the one in the archives.
The Skull and bones logo does look a little crude and hand painted, but the shoulder stripes being crisp are something I have come across before in the regular production, and is probably related to different painters and/or production centres.
Anyone bid on any of the action force in today's Vectis auction?
Some more prototypes in there. Picked up the GI Joe Flash for a reasonable price, but was outbid on the Z Force lot. Think the SAs lot and Enemy lot went for quite reasonable prices.
I tried for Stalker & yellow diver and did that SAS Panther have a grey bonnet?
Time of year was appaling for this auction.
The SAS panther bonnet was black and those pieces bagged up were just some boys childhood collection and not from a former employee, according to Vectis.
So anyone bidding on todays Vectics auction? Had a few interesting Action Force items.
The Scrap iron seems fairly reasonable, did have a whole in the bottom of the bubble but was still a nice example. Flash I was bidding on but went a bit out of my reach sadly.


text:
.. -*- coding: utf-8 -*-
.. URL: https://docs.docker.com/desktop/windows/troubleshoot/
   doc version: 19.03
      https://github.com/docker/docker.github.io/blob/master/docker-for-windows/troubleshoot.md
   doc version: 20.10
      https://github.com/docker/docker.github.io/blob/master/desktop/windows/troubleshoot.md
.. check date: 2022/05/14
.. Commits on Apr 20 2022 46b902e20a6248820e3ae94638b6c7895c20895e
.. -----------------------------------------------------------------------------

.. |whale| image:: ./images/whale-x.png
      :scale: 50%

.. Logs and troubleshooting
.. _win-logs-and-troubleshooting:

==================================================
ログとトラブルシューティング
==================================================

.. sidebar:: 目次

   .. contents::
       :depth: 3
       :local:

.. Did you know that Docker Desktop offers support for developers on a paid Docker subscription (Pro, Team, or Business)? Upgrade now to benefit from Docker Support. Click here to learn more.

.. hint:

   Docker Desktop は開発者をサポートする Docker サブスクリプション(Pro、Team、Business)を提供しているのをご存じでしょうか。アップグレードによって Docker サポートのメリットを得られます。詳細は :ruby:`こちら<mac-troubleshoot-support>` をご覧ください。

   * `今すぐアップグレード <https://www.docker.com/pricing>`_

.. This page contains information on how to diagnose and troubleshoot Docker Desktop issues, request Docker Desktop support, send logs and communicate with the Docker Desktop team, use our forums and Success Center, browse and log issues on GitHub, and find workarounds for known problems.

このページに含む情報は、どのようにして原因を追及し、問題を解決し、Docker Desktop のサポート要求、ログを送信し、Docker Desktop のチームとやりとりし、フォーラムやナレッジ・ハブで使ったり、GitHub 上で問題を見たり記録したり、既知の問題に対する回避策を発見する方法です。

.. Troubleshoot
.. _docker-win-trobuleshoot:

トラブルシュート
==================================================

.. Choose whale menu > Troubleshoot from the menu bar to see the troubleshoot options.

メニューバーにある Docker のアイコン |whale| > **Troubleshoot** を選択し、トラブルシュートのオプションを表示します。

.. image:: ./images/troubleshoot.png
   :scale: 60%
   :alt: Docker Desktop のトラブルシュート

.. The Troubleshoot page contains the following options:

トラブルシュートのページには、以下のオプションを含みます。

..    Restart Docker Desktop: Select to restart Docker Desktop.

* **Restart Docker Desktop** (Docker Desktop の再起動): 選択すると、Docker Desktop を再起動します。

.. Support: Users with a paid Docker subscription can use this option to send a support request. Other users can use this option to diagnose any issues in Docker Desktop. For more information, see Diagnose and feedback and Support.

* **Support** :有償 Docker サブスクリプション利用者は、このオプションを使ってサポートリクエストを送信できます。他の利用者がこのオプションを使うと、Docker Desktop 上のあらゆる問題を診断します。診断に関する詳細情報は、 :ref:`win-diagnose-and-feedback` をご覧ください。

..    Reset Kubernetes cluster: Select this option to delete all stacks and Kubernetes resources. For more information, see Kubernetes.

* **Reset Kubernetes cluster** (Kubernetes クラスタのリセット): このオプションを選択すると、全てのスタックと Kubernetes リソースを削除します。詳しい情報は :ref:`Kubernetes <win-kubernetes>` を御覧ください。

.. Clean / Purge data: This option resets all Docker data without a reset to factory defaults. Selecting this option results in the loss of existing settings.

.. Clean / Purge data: Select this option to delete container and image data. Choose whether you'd like to delete data from Hyper-V, WSL 2, or Windows Containers and then click Delete to confirm.

* **Clean / Purge data** (データ除去 / 削除):設定などを初期値のデフォルトに戻さず、全ての Docker データをリセットします。 Hyper-V 、 WSL 2 、 Windows コンテナーから、削除したいものを選び、確認してから **Delete** をクリックします。

..    Reset to factory defaults: Choose this option to reset all options on Docker Desktop to their initial state, the same as when Docker Desktop was first installed.

* **Reset to factory defaults** (初期値のデフォルトにリセット): このオプションを選択すると、Docker Desktop の全てのオプションを初期値にリセットし、Docker Desktop が始めてインストールされたのと同じ状態にします。

.. Diagnose and feedback
.. _win-diagnose-and-feedback:
診断とフィードバック
=======================================================

.. In-app diagnostics
.. _win-in-app-diagnostics:

アプリ内診断
--------------------------------------------------

.. If you experience issues for which you do not find solutions in this documentation, on Docker Desktop for Windows issues on GitHub, or the Docker Desktop for Windows forum, we can help you troubleshoot the log data. Before reporting an issue, we recommend that you read the information provided on this page to fix some common known issues.

発生した問題が、このページ内のドキュメントで解決できない場合は、 `GitHub の Docker Desktop <https://github.com/docker/for-mac/issues>`_ や `Docker Desktop for Mac forum <https://forums.docker.com/c/docker-for-mac>`_ で、ログデータのトラブルシュートに役立つ可能性があります。issue を報告する前に、いくつかの一般的に知られた問題を修正するため、このページが提供する情報を読むのをお勧めします。

.. Choose whale menu > Troubleshoot.

1. メニュー |whale| > **Troubleshoot** を選択します。

.. Optional: Sign into Docker Desktop. In addition, ensure you are signed into your Docker account.

2. オプション: Docker Desktop にサインイン。加えて、自分の `Docker アカウント <https://hub.docker.com/>`_ で入っているのを確認します。

.. Click Get support. This opens the in-app Support page and starts collecting the diagnostics. Diagnose & Feedback

3. **Get support** をクリック。これはアプリ内の **Support** ページを開き、診断情報の収集を開始します。

   .. image:: ./images/diagnose-support.png
      :scale: 60%
      :alt: 診断とフィードバック

.. When the diagnostics collection process is complete, click Upload to get a Diagnostic ID.

4. 診断情報の収集が終われば、 **Upload to get a Diagnostic ID** をクリックします。

.. When the diagnostics have been uploaded, Docker Desktop prints a diagnostic ID. Copy this ID.

5. 診断情報のアップロードが完了すると、 Docker Desktop は Diagnostic ID(診断 ID)を表示します。この ID をコピーします。

.. If you have a paid Docker subscription, click Contact Support. This opens the Docker Desktop support form. Fill in the information required and add the ID you copied earlier to the Diagnostics ID field. Click Submit to request Docker Desktop support.

6. 有償 Docker サブスクリプションを持っている場合は、 **Contact Support** をクリック。これは `Docker Desktop サポート <https://hub.docker.com/support/desktop/>`_ フォームを開きます。必要な情報を入力し、Diagnostics ID フィールドには先ほどコピーした ID を入れます。Docker Desktop サポートをリクエストするには **Submit** をクリックします。

   ..    Note
      You must be signed in to Docker Desktop using your Pro, Team, or Business tier credentials to access the support form. For information on what's covered as part of Docker Desktop support, see Support.

   .. note::

      サポートフォームにアクセスするには、Docker Desktop に Pro、Team、Business いずれかの認証賞情報でサインインしている必要があります。Docker Desktop サポートで扱う情報については、 :ref:`サポート <mac-troubleshoot-support>` をご覧ください。

.. If you don't have a paid Docker subscription, you can click Upgrade to benefit from Docker Support to upgrade your existing account. Alternatively, click Report a Bug to open a new Docker Desktop issue on GitHub. This opens Docker Desktop for Mac on GitHub in your web browser in a 'New issue' template. Complete the information required and ensure you add the diagnostic ID you copied earlier. Click submit new issue to create a new issue.

7. 有償 Docker サブスクリプションが無い場合、既存のアカウントをアップグレードするために **Upgrade to benefit from Docker Support** がクリック出来ます。あるいは、 **Report a Bug** をクリックし、GitHub に新しい Docker Desktop の issue を開きます。これは、GitHub 上の Docker Desktop `for Mac <https://github.com/docker/for-mac/issues/>`_ をブラウザで開き、「New issue」テンプレートを使います。必要情報を入力し、先ほどコピーした診断 ID を追加します。新しい issue を作成するには **submit new issue** をクリックします。

.. Diagnosing from the terminal
.. _win-diagnosing-from-the-terminal:

ターミナルから診断
--------------------------------------------------

.. On occasions it is useful to run the diagnostics yourself, for instance if Docker Desktop for Windows cannot start.

例えば Docker Desktop for Windows が開始できないなど、場合によっては自分での診断実行が役立つ場合もあります。

.. First locate the com.docker.diagnose, that should be in C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe.

まず :code:`com.docker.diagnose` を探します。大抵は :code:`C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe`
にあるでしょう。

.. To create and upload diagnostics, run:

診断の作成とアップロードをするには、次のコマンドを実行します:

.. code-block:: bash

   PS C:\> & "C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" gather -upload

.. After the diagnostics have finished, you should have the following output, containing your diagnostics ID:

診断が終了したら、以下のように診断 ID を含む出力になります。

.. code-block:: bash

   Diagnostics Bundle: C:\Users\User\AppData\Local\Temp\CD6CF862-9CBD-4007-9C2F-5FBE0572BBC2\20180720152545.zip
   Diagnostics ID:     CD6CF862-9CBD-4007-9C2F-5FBE0572BBC2/20180720152545 (uploaded)

.. If you have a paid Docker subscription, open the Docker Desktop support form. Fill in the information required and add the ID to the Diagnostics ID field. Click Submit to request Docker Desktop support.

有償 Docker サブスクリプションを持っている場合は、 **Contact Support** をクリック。これは `Docker Desktop サポート <https://hub.docker.com/support/desktop/>`_ フォームを開きます。必要な情報を入力し、Diagnostics ID フィールドには先ほどコピーした ID を入れます。Docker Desktop サポートをリクエストするには **Submit** をクリックします。

.. Self-diagnose tool
.. _win-self-diagnose-tool:
:ruby:`自己診断ツール <self-diagnose tool>`
--------------------------------------------------

.. Docker Desktop contains a self-diagnose tool which helps you to identify some common problems. Before you run the self-diagnose tool, locate com.docker.diagnose.exe. This is usually installed in C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe.

.. Docker Desktop contains a self-diagnose tool which helps you to identify some common problems. Before you run the self-diagnose tool, locate com.docker.diagnose. If you have installed Docker Desktop in the Applications directory, then the self-diagnose tool will be located at /Applications/Docker.app/Contents/MacOS/com.docker.diagnose.

Docker Desktop には、共通する問題を確認するのに役立つ自己診断ツールが入っています。自己診断ツールを実行する前に、 ``com.docker.diagnose`` を探します。アプリケーションのディレクトリ内に Docker Desktop をインストールしている場合は、自己診断ツールの場所は ``C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe`` です。

.. To run the self-diagnose tool, run:

自己診断ツールを実行するには、次のように実行します。

.. code-block:: bash

   PS C:\> & "C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" check

.. The tool runs a suite of checks and displays PASS or FAIL next to each check. If there are any failures, it highlights the most relevant at the end of the report.

ツールはチェックの一式を実行し、それぞれのチェックごとに **PASS** か **FAIL** を表示します。何らかのエラーがあれば、レポートの最後で最も関連する情報をハイライトで表示します。

..    Feedback
    Let us know your feedback on the self-diagnose tool by creating an issue in the for-mac GitHub repository.

.. note::

   **フィードバック**

   自己診断ツールのフィードバックを、 GitHub の `for-mac <https://github.com/docker/for-mac/issues>`_ リポジトリで issue を作成して教えてください。

.. Troubleshooting
.. _win-troubleshooting:
トラブルシューティング
==================================================

.. Make sure certificates are set up correctly
.. _win-make-sure-certificates-are-set-up-correctly:
証明書の正しいセットアップを確実にする
--------------------------------------------------

.. Docker Desktop ignores certificates listed under insecure registries, and does not send client certificates to them. Commands like docker run that attempt to pull from the registry produces error messages on the command line, for example:

Docker Desktop は安全ではないレジストリ(insecure registry)上にある証明書を無視します。また、そちらに対してクライアント証明書も送りません。 :code:`docker run` のようなコマンドでは、レジストリからの取得(pull)を試みても、次のようなコマンドライン上のエラーメッセージを表示します。

.. code-block:: bash

   Error response from daemon: Get http://192.168.203.139:5858/v2/: malformed HTTP response "\x15\x03\x01\x00\x02\x02"

.. As well as on the registry. For example:

レジストリ側でも同様にエラーが出ます。こちらが例です。

.. code-block:: bash

   2017/06/20 18:15:30 http: TLS handshake error from 192.168.203.139:52882: tls: client didn't provide a certificate
   2017/06/20 18:15:30 http: TLS handshake error from 192.168.203.139:52883: tls: first record does not look like a TLS handshake

.. For more about using client and server side certificates, see How do I add custom CA certificates? and How do I add client certificates? in the Getting Started topic.

クライアントとサーバ側証明書の使用に関しては、導入ガイドのトピックにある :ref:`win-add-custom-ca-certificates-server-side` と :ref:`win-add-client-certificates:` を御覧ください。

.. Volumes
.. _win-troubleshoot-volumes:
ボリューム
----------

.. Permissions errors on data directories for shared volumes
.. _permissions-errors-on-data-directories-for-shared-volumes:

共有ボリュームにおける、データ ディレクトリ上の権限(permission)エラー
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

.. Docker Desktop sets permissions on shared volumes to a default value of 0777 (read, write, execute permissions for user and for group).

Docker Desktop は :ref:`共有ボリューム <win-preferences-file-sharing>` 上の権限(パーミッション)をデフォルトで :code:`0777` ( :code:`ユーザ` 及び :code:`グループ` に対して、 :code:`読み込み` ・ :code:`書き込み` ・ :code:`実行` の権限)に設定します。

.. The default permissions on shared volumes are not configurable. If you are working with applications that require permissions different from the shared volume defaults at container runtime, you need to either use non-host-mounted volumes or find a way to make the applications work with the default file permissions.

共有ボリューム上におけるデフォルトの権限は、変更できません。もしも、アプリケーションの動作上、デフォルトの共有ボリューム上でコンテナ実行時に異なる権限が必要となる場合は、ホストをマウントしないボリュームを使用するか、アプリケーション側が初期設定の権限で動作する設定を見つける必要があります。

.. See also, Can I change permissions on shared volumes for container-specific deployment requirements? in the FAQs.

また、 :ref:`can-i-change-permissions-on-shared-volumes-for-container-specific-deployment-requirements` もご覧ください。

.. Volume mounting requires shared drives for Linux containers
.. _volume-mounting-requires-shared-drives-for-linux-containers:

共有ドライブ上へのボリューム マウントが Linux コンテナに必要です
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

.. If you are using mounted volumes and get runtime errors indicating an application file is not found, access is denied to a volume mount, or a service cannot start, such as when using Docker Compose, you might need to enable shared folders.

マウント ボリュームを使用中に、アプリケーション ファイルが見つからないというランタイム エラーが表示される場合は、ボリューム マウントに対するアクセスが拒否されているか、あるいは、 :doc:` Docker Compose </compose/gettingstarted>` などを使っていてサービスが開始できない場合には、  :ref:`共有フォルダ <<win-preferences-file-sharing>` の有効化が必要でしょう。

.. With the Hyper-V backend, mounting files from Windows requires shared folders for Linux containers. Click whale menu and then Settings > Shared Folders and share the folder that contains the Dockerfile and volume.

Hyper-V バックエンドで、Windows から Linux コンテナにボリュームをマウントするには、共有フォルダが必要です。Docker アイコンをクリックし、それから **Settings > Shared Folders** を選び、Dockerfile と ボリュームを置くためのフォルダを共有します。

.. Support for symlinks
.. _win-support-for-simlinks:

シンボリックリンク(symlinks)のサポート
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

.. Symlinks work within and across containers. To learn more, see How do symlinks work on Windows? in the FAQs.

シンボリックリンクはコンテナ間および横断して機能します。詳しく学ぶには、 FAQ の :ref:`how-do-symlinks-work-on-windows` をご覧ください。

.. Avoid unexpected syntax errors, use Unix style line endings for files in containers
.. _avoid-unexpected-syntax-errors,-use-unix-style-line-endings-for-files-in-containers:

予期しない構文エラー(unexpected syntax error)を避けるため、コンテナ内でファイルの行末を unix 風にする
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

.. Any file destined to run inside a container must use Unix style \n line endings. This includes files referenced at the command line for builds and in RUN commands in Docker files.

コンテナ内で実行するあらゆるファイルは、 Unix 風の行末 :code:`\n` を使う必要があります。これをファイルに含むのは、ビルド用のコマンドラインや Dockerfile における RUN 命令で参照するからです。

.. Docker containers and docker build run in a Unix environment, so files in containers must use Unix style line endings: \n, not Windows style: \r\n. Keep this in mind when authoring files such as shell scripts using Windows tools, where the default is likely to be Windows style line endings. These commands ultimately get passed to Unix commands inside a Unix based container (for example, a shell script passed to /bin/sh). If Windows style line endings are used, docker run fails with syntax errors.

Docker コンテナと :code:`docker build` の実行は Unix 環境のため、コンテナ内のファイルは Unix 風の行末 :code:`\n` を使うのが必須です。 Window 風の :code:`\r\n` ではありません。シェルスクリプトのようなファイルを作成するときは、Windows ツールを使うとデフォルトで Windows 風の行末になるので、気に留めておいてください。各コマンドは、最終的には Unix をベースするコンテナ内の Unix コマンドに渡されます(例えば、シェルスクリプトは :code:`/bin/sh` に渡されます)。もしも Windows 風の行末が用いられると、 :code:`docker run` は構文エラーになり失敗します。

.. For an example of this issue and the resolution, see this issue on GitHub: Docker RUN fails to execute shell script.

この問題と解決方法の例は、GitHub 上の issue を御覧ください:  `Docker RUN でシェルスクリプトの実行に失敗する(英語) <https://github.com/moby/moby/issues/24388)>`_

.. Path conversion on Windows
.. _path-conversion-on-windows:
Windows 上でのパス変換
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

.. On Linux, the system takes care of mounting a path to another path. For example, when you run the following command on Linux:

Linux 上では、マウントしているパスを、他のパスへと管理しています。たとえば、Linux 上で以下のコマンドを実行するとします。

.. code-block:: bash

   $ docker run --rm -ti -v /home/user/work:/work alpine

.. It adds a /work directory to the target container to mirror the specified path.

これは対象のコンテナに ``/work`` ディレクトリを追加し、指定したパスの内容をミラーします。

.. However, on Windows, you must update the source path. For example, if you are using the legacy Windows shell (cmd.exe), you can use the following command:

しかしながら、Windows 上では、元のパス(ソース パス)を変更する必要があります。たとえば、レガシーの Windows シェル( ``cmd.exe`` )を使っている場合、以下のコマンドが使えます。

.. code-block:: bash

   $ docker run --rm -ti -v C:\Users\user\work:/work alpine

.. This starts the container and ensures the volume becomes usable. This is possible because Docker Desktop detects the Windows-style path and provides the appropriate conversion to mount the directory.

これはコンテナを起動し、ボリュームを利用可能な状態にします。Docker Desktop は Windows 形式のパスを見つけると、ディレクトリをマウントするため、適切に変換する場合があります。

.. Docker Desktop also allows you to use Unix-style path to the appropriate format. For example:

Docker Desktop でも適切な形式で Unix 風のパスを指定できます。例:

.. code-block:: bash

   $ docker run --rm -ti -v /c/Users/user/work:/work alpine ls /work

.. Working with Git Bash
.. _working-with-git-bash:
Git Bash で動かす
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

.. Git Bash (or MSYS) provides Unix-like environment on Windows. These tools apply their own preprocessing on the command line. For example, if you run the following command in Git Bash, it gives an error:

.. code-block:: bash

   $ docker run --rm -ti -v C:\Users\user\work:/work alpine
   docker: Error response from daemon: mkdir C:UsersUserwork: Access is denied.

.. This is because the \ character has a special meaning in Git Bash. If you are using Git Bash, you must neutralize it using \\:

エラーになるのは、 Git Bush では ``\`` 記号が特別な意味を持つためです。Bit Bash を使う場合は、無効化する ``\\`` を使う必要があります。

.. code-block:: bash

   $ docker run --rm -ti -v C:\\Users\\user\\work:/work alpine

.. Also, in scripts, the pwd command is used to avoid hardcoding file system locations. Its output is a Unix-style path.

また、スクリプト内で ``pwd`` コマンドを使う場合は、ファイルシステムの場所をハードコーディングしないように使われます。出力は Unix 風のパスです。

.. code-block:: bash

   $ pwd
   /c/Users/user/work

.. Combined with the $() syntax, the command below works on Linux, however, it fails on Git Bash.

``$()`` 構文を組み合わせる場合、 Linux では以下のコマンドは動作しますが、 Git Bash では失敗します。

.. code-block:: bash

   $ docker run --rm -ti -v $(pwd):/work alpine
   docker: Error response from daemon: OCI runtime create failed: invalid mount {Destination:\Program Files\Git\work Type:bind Source:/run/desktop/mnt/host/c/Users/user/work;C Options:[rbind rprivate]}: mount destination \Program Files\Git\work not absolute: unknown.

.. You can work around this issue by using an extra /

この問題に対応するには、追加の ``/`` を使います。

.. code-block:: bash

   $ docker run --rm -ti -v /$(pwd):/work alpine

.. Portability of the scripts is not affected as Linux treats multiple / as a single entry. Each occurence of paths on a single line must be neutralized.

Linux は複数の ``/`` を1つの入力として扱うため、スクリプトの互換性には影響ありません。1行でパスを扱う場合は、無効化する必要があります。

.. code-block:: bash

   $ docker run --rm -ti -v /$(pwd):/work alpine ls /work
   ls: C:/Program Files/Git/work: No such file or directory

.. In this example, The $(pwd) is not converted because of the preceding '/'. However, the second '/work' is transformed by the POSIX layer before passing it to Docker Desktop. You can also work around this issue by using an extra /.

この例では、 ``/`` が先にあるため、  ``$(pwd)`` は変換されません。ですが、2つめの ``/work`` は Docker Desktop で処理する前に、 POSIX レイヤーによって変換されます。これを正しく動作するには、 ``/`` を追加します。

.. code-block:: bash

   $ docker run --rm -ti -v /$(pwd):/work alpine ls //work

.. To verify whether the errors are generated from your script, or from another source, you can use an environment variable. For example:

スクリプトや他のソースでエラーが発生する場合、どこか原因かを確認するには、環境変数が使えます。例:

.. code-block:: bash

   $ MSYS_NO_PATHCONV=1 docker run --rm -ti -v $(pwd):/work alpine ls /work

.. It only expects the environment variable here. The value doesn't matter.

ここでは、環境変数そのものを想定しています。(環境変数の)値は関係ありません。

.. In some cases, MSYS also transforms colons to semicolon. Similar conversions can also occur when using ~ because the POSIX layer translates it to a DOS path. MSYS_NO_PATHCONV also works in this case.

場合によっては、 MSYS もコロンをセミコロンに変換します。 ``~`` を使う時、 POSIX レイヤーが DOS のパスに変更する時に発生する状況と似ています。この場合、 ``MSYS_NO_PATHCONV`` も動作します。

.. Virtualization
.. _win-troubleshoot-virtualization:
仮想化
--------------------

.. Your machine must have the following features for Docker Desktop to function correctly:

Docker Desktop を正しく機能するには、マシンには以下の機能が必要です。

.. WSL 2 and Windows Home
.. _wsl-2-and-windows-home:
WSL 2 と Windows Home
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

..   Virtual Machine Platform
    Windows Subsystem for Linux
    Virtualization enabled in the BIOS
    Hypervisor enabled at Windows startup

1. 仮想マシン プラットフォーム
2. `Linux 用 Windows サブシステム (WSL) <https://docs.microsoft.com/ja-jp/windows/wsl/install>`_
3. `BIOS で仮想化を有効 <https://bce.berkeley.edu/enabling-virtualization-in-your-pc-bios.html>`_
4. Windows 起動時にハイパーバイザーを有効化

.. Hyper-V
.. _win-troubleshoot-hyper-v:

Hyper-V
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

.. On Windows 10 Pro or Enterprise, you can also use Hyper-V with the following features enabled:

Windows 10 Pro や Enterprise では、以下の機能を有効にして Hyper-V も使えます。

..    Hyper-V installed and working
    Virtualization enabled in the BIOS

1. `Hyper-V <https://docs.microsoft.com/ja-jp/windows-server/virtualization/hyper-v/hyper-v-technology-overview>`_ をインストールして、動作させる
2. `BIOS で仮想化の有効化 <https://bce.berkeley.edu/enabling-virtualization-in-your-pc-bios.html>`_
3. Windows 起動時にハイパーバイザーを有効化

.. image:: ./images/hyperv-enabled.png
   :scale: 60%
   :alt: Windows 機能の Hyper-V

.. Docker Desktop requires Hyper-V as well as the Hyper-V Module for Windows Powershell to be installed and enabled. The Docker Desktop installer enables it for you.

Docker Desktop をインストールして有効化するには、 Hyper-V と同様に Windows Powershell 用 Hyper-V モジュールも必要です。Docker Desktop インストーラは、これらを有効化します。

.. Docker Desktop also needs two CPU hardware features to use Hyper-V: Virtualization and Second Level Address Translation (SLAT), which is also called Rapid Virtualization Indexing (RVI). On some systems, Virtualization must be enabled in the BIOS. The steps required are vendor-specific, but typically the BIOS option is called Virtualization Technology (VTx) or something similar. Run the command systeminfo to check all required Hyper-V features. See Pre-requisites for Hyper-V on Windows 10 for more details.

また、Docker Desktop は Hyper-V を使うために2つの CPU 機能を使います。すなわち、仮想化と  Rapid Virtualization Indexing (RVI) とも呼ばれる Second Level Address Translation (SLAT) です。同じシステムの BIOS 上で、Virtualization (仮想化)の有効化が必須です。必要な手順はベンダによって異なりますが、典型的な BIOS オプションは :code:`Virtualization Technology (VTx)` と呼ばれるものか、似たようなものです。Hyper-V 機能が必要とする全てを確認するには、 :code:`systeminfo` コマンドを実行します。詳細は `Windows 10 Hyper-V のシステム要件 <https://docs.microsoft.com/ja-jp/virtualization/hyper-v-on-windows/reference/hyper-v-requirements>`_ を御覧ください。

.. To install Hyper-V manually, see Install Hyper-V on Windows 10. A reboot is required after installation. If you install Hyper-V without rebooting, Docker Desktop does not work correctly.

Hyper-V を手動でインストールするには、 `Windows 10 上に Hyper-V をインストールする <https://msdn.microsoft.com/en-us/virtualization/hyperv_on_windows/quick_start/walkthrough_install>`_ を御覧ください。インストール後は再起動が必要です。Hyper-V をインストールしても再起動をしないと、 Docker Desktop は正しく動作しません。

.. From the start menu, type Turn Windows features on or off and press enter. In the subsequent screen, verify that Hyper-V is enabled:

スタートメニューから、 **Windows 機能の有効化又は無効化** を入力し、エンターを押します。以下の画面のようになっていると、Hyper-V は有効です。

.. Virtualization must be enabled
.. _virtualization-must-be-enabled:

仮想化を必ず有効化
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

.. In addition to Hyper-V or WSL 2, virtualization must be enabled. Check the Performance tab on the Task Manager:

:ref:`Hyper-V <win-troubleshoot-hyper-v>` や :doc:`WSL 2 <wsl>` を追加するには、仮想化の有効化が必要です。タスクマネージャー上のパフォーマンス タブをクリックします。

.. image:: ./images/virtualization-enabled.png
   :scale: 60%
   :alt: タスクマネージャー

.. If you manually uninstall Hyper-V, WSL 2 or disable virtualization, Docker Desktop cannot start. See Unable to run Docker for Windows on Windows 10 Enterprise.

もしも Hyper-V を手動でアンインストールするか、仮想化を無効にしたら、Docker Desktop は起動できません。 [Windows 10 Enterprise では Docker for Windows を実行できません(英語)](https://github.com/docker/for-win/issues/74) を御覧ください。

.. Hypervisor enabled at Windows startup
.. _hypervisor-enabled-at-windows-startup:
Windows のスタートアップでハイパーバイザを有効化
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

.. If you have completed the steps described above and are still experiencing Docker Desktop startup issues, this could be because the Hypervisor is installed, but not launched during Windows startup. Some tools (such as older versions of Virtual Box) and video game installers disable hypervisor on boot. To reenable it:

前述の手順を全て実施しても Docker Desktop の起動に問題が出ている場合は、ハイパーバイザーはインストールされているものの、Windows のスタートアップ(起動処理)中に起動できていない可能性があります。同様のツール(Virtual Box の古いバージョン)やビデオゲームのインストーラが、起動時にハイパーバイザーを無効化します。再度、有効化するには、次の手順をします。

..  Open an administrative console prompt.
    Run bcdedit /set hypervisorlaunchtype auto.
    Restart Windows.

1. 管理者としてコマンドプロンプトを開く。
2. ``bcdedit /set hypervisorlaunchtype auto`` を実行
3. Windows 再起動

.. You can also refer to the Microsoft TechNet article on Code flow guard (CFG) settings.

また、 `Microsoft TechNet の記事 <https://social.technet.microsoft.com/Forums/en-US/ee5b1d6b-09e2-49f3-a52c-820aafc316f9/hyperv-doesnt-work-after-upgrade-to-windows-10-1809?forum=win10itprovirt>`_ にある Code flow guard (CFG) 設定もご覧ください。

.. Windows containers and Windows Server
.. _windows-containers-and-windows-server:

Windows コンテナーと Windows Server
--------------------------------------------------

.. Docker Desktop is not supported on Windows Server. If you have questions about how to run Windows containers on Windows 10, see Switch between Windows and Linux containers.

Windows Server 上での Docker Desktop はサポート外です。Windows 10 上で Windows コンテナの実行に関する疑問があれば、 :ref:`switch-between-windows-and-linux-containers` を御覧ください。

.. A full tutorial is available in docker/labs on Getting Started with Windows Containers.

`docker/labs  <https://github.com/docker/labs>`_ の `Getting Started with Windows Container <https://github.com/docker/labs/blob/master/windows/windows-containers/README.md>`_ に全てのチュートリアルがあります。
..
.. You can install a native Windows binary which allows you to develop and run Windows containers without Docker Desktop. However, if you install Docker this way, you cannot develop or run Linux containers. If you try to run a Linux container on the native Docker daemon, an error occurs:

ネイティブな Windows バイナリをインストールしたら、Windows Desktop がなくても Windows コンテナの開発と実行が可能です。しかし、この方法で Docker をインストールしたら、Linux コンテナの開発と実行ができません。もしもネイティブな Docker デーモンで Linux コンテナの実行を試みても、次のようなエラーが発生します。

.. code-block:: bash

   C:\Program Files\Docker\docker.exe:
    image operating system "linux" cannot be used on this platform.
    See 'C:\Program Files\Docker\docker.exe run --help'.

.. Running Docker Desktop in nested virtualization scenarios
.. _running-docker-desktop-in-nested-virtualization-scenarios-win:
ネストした仮想化環境で Docker Desktop を実行
--------------------------------------------------

.. Docker Desktop can run inside a Windows 10 VM running on apps like Parallels or VMware Fusion on a Mac provided that the VM is properly configured. However, problems and intermittent failures may still occur due to the way these apps virtualize the hardware. For these reasons, Docker Desktop is not supported in nested virtualization scenarios. It might work in some cases, and not in others.

Paralles や VMware Fusion a Mac 上で動く Windows 10 仮想マシン内で、適切な設定をすると Docker Desktop を実行可能です。しかしながら、ハードウェア仮想化アプリの手法によって、問題や一時的な問題が発生する可能性があります。そのため、 **Docker Desktop はネストした仮想化環境での実行をサポートしません** 。動く場合もあれば、動かない場合もあります。

.. For best results, we recommend you run Docker Desktop natively on a Windows system (to work with Windows or Linux containers), or on Mac to work with Linux containers.

最良の結果を出すには、Windows システム上で Docker Desktop をネイティブに実行するのを推奨します(Windows コンテナも Linux コンテナも動作します)。また Mac では Linux コンテナのみ動作します。

.. If you still want to use nested virtualization
.. _if-you-still-want-to-use-nested-virtualization:
それでもネスト化した仮想化環境を使いたい場合には
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

..    Make sure nested virtualization support is enabled in VMWare or Parallels. Check the settings in Hardware > CPU & Memory > Advanced Options > Enable nested virtualization (the exact menu sequence might vary slightly).
    Configure your VM with at least 2 CPUs and sufficient memory to run your workloads.
    Make sure your system is more or less idle.
    Make sure your Windows OS is up-to-date. There have been several issues with some insider builds.
    The processor you have may also be relevant. For example, Westmere based Mac Pros have some additional hardware virtualization features over Nehalem based Mac Pros and so do newer generations of Intel processors.

* VMware や Paralles でネスト化した仮想化サポートが有効になっているかどうかを確認します。設定の **Hardware > CPU & Memory > Advanced Options > Enable nested virtualization** を確認します(展開するメニュー順番は、若干変わるかもしれません)。
* 仮想マシンが最小 2 CPU と、ワークロードを実行するための十分なメモリを使うように設定します。
* システムは多少のアイドル(余裕)があるようにします。
* Windows OS を最新版へ確実に更新します。insider ビルドによっては、複数の問題があります。
* 適切なプロセッサも必要です。例えば、Westmere ベースの Mac Pro は、Nehalem ベースの Mac Pro よりもハードウェア仮想化機能が追加されていますし、更に新しい世代のインテル プロセッサもそうでしょう。

.. Typical failures we see with nested virtualization
.. _typical-failures-we-see-with-nested-virtualization:
ネスト化した仮想化環境で起こる典型的な問題
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

..    Slow boot time of the Linux VM. If you look in the logs and find some entries prefixed with Moby. On real hardware, it takes 5-10 seconds to boot the Linux VM; roughly the time between the Connected log entry and the * Starting Docker ... [ ok ] log entry. If you boot the Linux VM inside a Windows VM, this may take considerably longer. We have a timeout of 60s or so. If the VM hasn't started by that time, we retry. If the retry fails we print an error. You can sometimes work around this by providing more resources to the Windows VM.

* Linux 仮想マシンのブート時に確認します。ログを見て、 :code:`Moby` を先頭に含む行がないかどうか調べます。実在のハードウェアでは、Linux 仮想マシンのブートにかかる時間は 5 ~ 10 秒です。つまり、おおよその時間は、 :code:`Connected`  のログ記録から :code:`* Starting Docker ... [OK]` ログ記録までです。もしも Windows 仮想マシン内で Linux 仮想マシンをブートするのであれば、この処理にかかる時間はより長くなります。タイムアウトは 60 秒以上です。もし VM が時間までに起動しなければ、リトライします。リトライに失敗したら、エラーを表示します。Windows 仮想マシンに対し、更にリソースを提供することで回避可能な場合があります。

..    Sometimes the VM fails to boot when Linux tries to calibrate the time stamp counter (TSC). This process is quite timing sensitive and may fail when executed inside a VM which itself runs inside a VM. CPU utilization is also likely to be higher.

* ブート時、タイムスタンプ・カウンタ(TSC)の補正を Linux が行うとき、仮想マシンが落ちる場合があります。この処理はタイミングがセンシティブなため、仮想マシン内で仮想マシンを実行する場合に落ちるかもしれません。また、 CPU 使用率も高くなります。

..    Ensure "PMU Virtualization" is turned off in Parallels on Macs. Check the settings in Hardware > CPU & Memory > Advanced Settings > PMU Virtualization.

* Paralles on Mac では "PMU Virtualizatoin" が無効かどうかを確認します。 設定の **Hardware > CPU & Memory > Advanced Settings > PMU Virtualization** を確認します。

.. Networking issues
.. _win-networking-issues:
ネットワーク機能の問題
------------------------------

.. IPv6 is not (yet) supported on Docker Desktop.

Docker Desktop は(まだ) IPv6 をサポートしていません。

.. Workarounds
.. _win-workarounds:
回避策(ワークアラウンド)
==============================

.. Reboot
.. _win-reboot:
再起動
--------------------------------------------------

.. Restart your PC to stop / discard any vestige of the daemon running from the previously installed version.

PC を再起動し、以前にインストールしたバージョンで動いているデーモンの残骸を、停止・削除します。

.. Unset DOCKER_HOST
.. _win-unset-docker-host:
:code:`DOCKER_HOST` のリセット(unset)
--------------------------------------------------

.. The DOCKER_HOST environmental variable does not need to be set. If you use bash, use the command unset ${!DOCKER_*} to unset it. For other shells, consult the shell's documentation.

:code:`DOCKER_HOST` 環境変数の設定は不要です。 bash を使用する場合は、リセットのために :code:`unset ${!DOCKER_*}` コマンドを使います。他のシェルの場合は、シェルのドキュメントをご確認ください。

.. Make sure Docker is running for webserver examples
.. _win-make-sure-docker-is-running-for-webserver-examples:
ウェブサーバの例で Docker が動作しているのを確認
--------------------------------------------------

.. For the hello-world-nginx example and others, Docker Desktop must be running to get to the webserver on http://localhost/. Make sure that the Docker whale is showing in the menu bar, and that you run the Docker commands in a shell that is connected to the Docker Desktop Engine (not Engine from Toolbox). Otherwise, you might start the webserver container but get a "web page not available" error when you go to docker.

``hello-world-nginx`` サンプルなどを使い、 Docker Desktop で ``https://localhost`` 上にウェブサーバを起動します。メニューバー上に Docker 鯨(のアイコン)があるのを確認し、シェル上の Docker コマンドが Docker Desktop エンジンに接続しているのを確認します(Toolbox のエンジンではありません)。そうしなければ、ウェブサーバ・コンテナは実行できるかもしれませんが、 ``docker`` は "web page not available"(ウェブページが表示できません)というエラーを返すでしょう。

.. How to solve port already allocated errors
.. _win-how-to-solve-port-already-allocated-errors:
``port already allocated`` (ポートが既に割り当てられています) エラーを解決するには
--------------------------------------------------------------------------------------

.. If you see errors like Bind for 0.0.0.0:8080 failed: port is already allocated or listen tcp:0.0.0.0:8080: bind: address is already in use ...

``Bind for 0.0.0.0:8080 failed: port is already allocated`` や ``listen tcp:0.0.0.0:8080: bind: address is already in use`` ... のようなエラーが出ることがあるでしょう。

.. These errors are often caused by some other software on Windows using those ports. To discover the identity of this software, either use the resmon.exe GUI and click "Network" and then "Listening Ports" or in a Powershell use netstat -aon | find /i "listening " to discover the PID of the process currently using the port (the PID is the number in the rightmost column). Decide whether to shut the other process down, or to use a different port in your docker app.

これらのエラーは、Windows 上の他のソフトウェアが各ポートを使っている場合によく発生します。どのソフトウェアが使っているかを見つけるか、 ``resmon.exe`` の GUI を使い "Network" と "listening Ports"  をクリックするか、 Powershell 上では ``netstat -aon | find /i "listening "`` を使って、対象ポートを現在使っているプロセスの PID を見つけます(PID の値は行の右端です)。他のプロセスの停止を決めるか、あるいは、docker アプリで別のポートを使うかを決めます。

.. Docker Desktop fails to start when anti-virus software is installed
.. _win-docker-desktop-fails-to-start-when-anti-virus-software-is-installed:
アンチウィルス ソフトウェアをインストールしていると、Docker Desktop の起動に失敗
-------------------------------------------------------------------------------------

.. Some anti-virus software may be incompatible with Hyper-V and Microsoft Windows 10 builds. The conflict typically occurs after a Windows update and manifests as an error response from the Docker daemon and a Docker Desktop start failure.

いくつかのアンチウィルス ソフトウェアは、Hyper-V と Microsoft Windows 10 ビルドによっては互換性がない場合があります。典型的に発生するのは Windows update 直後で、Docker デーモンからエラーの反応が表示され、Docker Desktop の起動に失敗します。

.. For a temporary workaround, uninstall the anti-virus software, or explore other workarounds suggested on Docker Desktop forums.

一時的な回避策としては、アンチウィルス ソフトウェアをアンインストールするか、Docker Desktop フォーラム上での他の回避策をお探しください。

.. Support
.. _mac-support:
サポート
==========

.. This section contains instructions on how to get support, and covers the scope of Docker Desktop support.

このセクションでは、サポートを得る手順と、 Docker Desktop のサポート範囲を扱います。

.. This feature requires a paid Docker subscription
.. Docker Desktop offers support for developers subscribed to a Pro, Team, or a Business tier. Upgrade now to benefit from Docker Support.

.. note::

   **この機能は有償 Docker サブスクリプションが必要です**

   Docker Desktop は Pro、Team、Business を契約している開発者向けにサポートを提供します。Docker サポートの利点を得るには、いますぐアップグレードしましょう。

   `いますぐアップグレード <https://www.docker.com/pricing>`_

.. How do I get Docker Desktop support?
.. _mac-how-do-i-get-docker-desktop-support:
Docker Desktop のサポートを得るには
----------------------------------------

.. If you have a paid Docker subscription, please raise a ticket through Docker Desktop support.

有償 Docker サブスクリプションがあれば、 `Docker Desktop support <https://hub.docker.com/support/desktop/>`_ を通してチケットを上げてください。

.. Docker Community users can get support through our Github repos for-win and for-mac, where we respond on a best-effort basis.

Docker Community 利用者は、 Github リポジトリ for-win と for-mac を通してサポートを得られますが、対応は基本的にベストエフォートです。

.. What support can I get?
.. _mac-what-support-can-i-get:
何のサポートを得られるのか
----------------------------------------

.. If you have a paid Docker subscription, you can request for support on the following types of issues:

有償 Docker サブスクリプションを持っていれば、以下の種類の問題に対するサポートを要求できます。

..  Desktop upgrade issues
    Desktop installation issues
        Installation crashes
        Failure to launch Docker Desktop on first run
    Usage issues
        Crash closing software
        Docker Desktop not behaving as expected
    Configuration issues
    Basic product 'how to' questions

* Desktop アップグレードの問題
* Desktop インストールの問題

  * インストールのクラッシュ
  * Docker Desktop 初回実行時のエラー

* 利用に関係する問題

  * クラッシュによってソフトウェアが閉じる
  * Docker Desktop が期待通りの挙動をしない

* 設定に関する問題
* 基本的なプロダクトの「使い方」の質問

.. What is not supported?
.. _mac-what-is-not-supported:
何がサポートされないか
------------------------------

.. Docker Desktop excludes support for the following types of issues:

Docker Desktop のサポートから、以下の種類の問題は対象外です。

..  Use on or in conjunction with hardware or software other than that specified in the applicable documentation
    Running on unsupported operating systems, including beta/preview versions of operating systems
    Running containers of a different architecture using emulation
    Support for the Docker engine, Docker CLI, or other bundled Linux components
    Support for Kubernetes
    Features labeled as experimental
    System/Server administration activities
    Supporting Desktop as a production runtime
    Scale deployment/multi-machine installation of Desktop
    Routine product maintenance (data backup, cleaning disk space and configuring log rotation)
    Third-party applications not provided by Docker
    Altered or modified Docker software
    Defects in the Docker software due to hardware malfunction, abuse, or improper use
    Any version of the Docker software other than the latest version
    Reimbursing and expenses spent for third-party services not provided by Docker
    Docker Support excludes training, customization, and integration

* ドキュメントで対象としていないハードウェアやソフトウェアに関連する使い方
* サポートしていないオペレーティングシステム上での実行で、オペレーティングシステムのベータもしくはプレビューバージョンも含む
* エミュレーションを使用し、異なるアーキテクチャのコンテナを実行
* Docker Engine、 Docker CLI 、あるいは他に同梱されている Linux コンポーネントに対するサポート
* Kubernetes サポート
* 実験的と表記されている機能
* システムやサーバ管理の取り組み
* 本番環境での Desktop 実行に関するサポート
* Desktop をスケールするデプロイや複数マシンへのインストール
* 定期的なプロダクトのメンテナンス(データバックアップ、ディスク容量をあけたり、ログローテーションの設定)
* Docker によって知恵教されていないサードパーティ製アプリケーション
* Docker ソフトウェアの改変や編集
* ハードウェア故障、不正利用、不適切な利用による Docker ソフトウェアの不具合
* 最新バージョンではない、あらゆる古いバージョンの Docker ソフトウェア
* Docker が提供していないサードパーティ製サービスに対する補償や費用請求
* Docker サポートから、トレーニング、カスタマイズ、インテグレーションは除外

.. What versions are supported?
.. _mac-what-versions-are-supported:
どのバージョンがサポート対象ですか?
----------------------------------------

.. We currently only offer support for the latest version of Docker Desktop. If you are running an older version, you may be asked to upgrade before we investigate your support request.

現在サポートを提供しているのは、 Docker Desktop の最新バージョンのみです。古いバージョンを実行している場合は、私たちに調査のサポートリクエストを送る前に、最新バージョンへのアップグレードを確認ください。

.. How many machines can I get support for Docker Desktop on?
Docker Desktop のサポートを何台まで受けられますか?
------------------------------------------------------------

.. As a Pro user you can get support for Docker Desktop on a single machine. As a Team, you can get support for Docker Desktop for the number of machines equal to the number of seats as part of your plan.

Pro の利用者であれば、1台のマシン上の Docker Desktop にサポートを得られます。Team であれば、プランの一部として、契約数と同等の数の Docker Desktop のサポートが得られます。

.. What OS's are supported?
.. _mac-what-oss-are-supported:
どの OS がサポートされますか?
----------------------------------------

.. Docker Desktop is available for Mac and Windows. The supported version information can be found on the following pages:

Docker Desktop は Mac と Windows 上で利用できます。サポート対象のバージョン情報は、以下のページで確認できます。

..  Mac system requirements
    Windows system requirements

* :ref:`Mac システム動作条件 <mac-system-requirements>`
* :ref:`Windows システム動作条件 <win-system-requirements>`

.. Can I run Docker Desktop on Virtualized hardware?
.. _mac-can-i-run-docker-desktop-on-virtualized-hardware:
仮想化ハードウェア上で Docker Desktop は実行できますか?
----------------------------------------------------------------------

.. No, currently this is unsupported and against the terms of use.

いいえ、現時点ではサポート外で、利用規約は適用されません。

.. seealso::

   Logs and troubleshooting
      https://docs.docker.com/desktop/windows/troubleshoot/Logs and troubleshooting

redpajama_set_name: RedPajamaGithub


Impact Events is a full service event production company that specializes in technical and creative support for corporate events, business meetings, and social venues to the Southeast Michigan, Detroit area.
Our mission is to provide you with high quality and innovative equipment and service. When it comes to production companies, equipment is equipment. Service and creativity is what sets us apart from the rest. We strive for outstanding customer satisfaction by working as a team with you. The relationships we build with you are one of mutual respect and long term.


text:
Coordination of the EUSBSR
Benefits of transnational cooperation: 10 things to know
Interreg30years
Interreg Storymap
EU Strategy for the Baltic Sea Region
Contributions 2014-2020
Apply for funds
Regular project calls
Project platform calls
Extension stage calls
Second call for extension stage applications
Seed Money calls
EUSBSR coordination calls
National Information
First Level Control
Visibility rules
Visibility downloads
BAMOS
Future Programme
Monitoring Committee
Managing Authority/Joint Secretariat
How Interreg makes electronics green
Next-generation large windmills, solar power plants and electric cars can become more reliable and efficient thanks to advanced power electronics. These new technologies are in fact among the key drivers for reducing energy consumption and CO2 emissions. The Interreg Baltic Sea Region project Green PE explored the new terrain for using green advanced power electronics together with academia, technology transfer organisations and industry around the Baltic Sea.
© PantherMedia / AndrewLozovyi
It's all about power
Power electronics is about mastering electric apparatus: from smart energy use in high resolution flat screens to efficient energy conversion in huge wind turbine generators. Power electronics that is based on next generation materials is called advanced power electronics.
New technologies used by advanced power electronics allow for more than 50% energy savings thanks to reducing energy losses at all levels of the energy supply chain. The challenge the Green PE faced were, however, prejudices against sustainable power electronics-based solutions as well as some technological and economical barriers.
Power electronics turning green
With more than 15,000 companies in the Baltic Sea region dealing with power electronics, a transition towards a greener society using clean, secure and safe energy is within the arm's reach. During its activities, Green PE addressed small and medium sized enterprises to help them adopt advanced power electronics successfully. Green PE involved research, technological transfer and company partners, and showed how technological and economic barriers as well as knowledge gaps can be overcome in order to accelerate the innovation cycle and achieve a faster market acceptance of the energy efficient novel technologies.
Green PE pilot activities
Green PE demonstrated the potential of advanced power electronics in test cases in three relevant for the Baltic Sea Region sectors: renewable energies, e-mobility and smart houses.
Boosting the performance of electric race cars
© PantherMedia / Marko Beric
On an example of a racing car, Green PE proved that using next generation materials, such as silicon carbide, improves the traction systems in electric vehicles but does not increase the production costs.
A prototype of a battery conditioner for an electric motor based on silicon carbide was produced by the Latvian company Drive eO. Thanks to prior research by the University of Latvia, Warsaw University, and the University of Southern Denmark, new engines gained more power and system voltage. "There is no doubt that silicon carbide power electronics will soon be adopted into series production," said Kristaps Dambis, Project Director from Drive eO. Why? Because any increase in the system efficiency may enlarge the range of the vehicle. Now, newly equipped racing cars enter Formula Student E in the campus sites in Odense and Sønderborg.
Giving power to clean renewable energy sources
In order to use new sources of renewable energies more efficiently, such as large scale photovoltaics, offshore wind and large-scale bioenergy, changes in the power electronics modules on the element level (e.g. transistors) is a necessity. Green PE installed a power converter with the highest light load efficiency for renewable energy application. Using gallium nitride transistors substantially increased power density generated from photovoltaics, e.g. from PV panels that capture the sun's energy to convert it into electricity.
Smart house refurbishment to save energy
Efficient power conversion systems are an essential prerequisite for smart houses. A house in Swedish Växjö, which was already equipped with solar panels and solar collectors, was upgraded with energy storage capability and an additional direct current appliances network. By creating a stand-alone efficient solar system that works even in the case of power outages, Green PE proved the advantages of using advanced power electronics in an ordinary household. "The smart houses concept (…) with a direct current grid and islandic capability is of strong interest for companies and funding agencies in Sweden," said Teresita Qvarnström from RISE Research Institutes of Sweden, highlighting they will further develop the tool to increase the resilience of the energy infrastructure in case of power outages.
Transfer of knowledge in a transnational spirit
The project Green PE has successfully reached out to small and medium sized enterprises in the Baltic Sea region. So far, 240 companies actively engaged in the project activities and around 7,000 enterprises were reached via technology transfer partners. The project also conducted 80 company visits and over a dozen consultations on introducing advanced power electronics technologies in seven Baltic Sea countries. Thanks to an in-depth analysis on the state-of-the-art in advanced power electronics, and defining factors driving and hindering the technology uptake in Denmark, Germany, Lithuania, Latvia, Poland and Sweden, Green PE took an active role in shaping the future of power electronics in the region.
The future power of advanced power electronics
"Advanced power electronics is a rapidly developing field in the Baltic Sea region, and the Green PE project has given a great opportunity to see what activities are taking place in other countries," said dr hab. sc. Ing. Janis Stabulnieks, Managing Director from the Latvian Technological Centre. The project set up a transnational collaboration platform for research institutions and companies, especially innovative start-ups and SMEs around the Baltic Sea, to ensure the transfer of knowledge and to build up research and innovation alliances across borders.
As an example of such alliances is the Centre for Industrial Electronics. It was set up at the Danish-German border as a joint endeavour of industry, academia, regions and municipalities. Its functioning is planned until at least 2030, and it covers projects among others Germany, Denmark and Sweden, Latvia and Estonia.
With convincing pilot activities, clear roadmaps, and technology consultations, Green PE increased the capacities of enterprises around the Baltic Sea region to use green energy smarter, and by this emit smaller amounts of CO2. Not only does advanced power electronics generate revenues for enterprises, but it is beneficial for the environment, too. A true win-win situation for enterprises and, even more importantly, the people.
Article compiled by Anna Gałyga based on Green PE application to RegioStars awards & Green PE brochure on project findings.
Green PE entry in the project library
Managing Authority /
IB.SH
Grubenstraße 20
18055 Rostock, Germany
info@interreg-baltic.eu
Joint Secretariat – Riga branch office
Latvian State Regional Development Agency
Alberta Iela 10
LV-1010, Riga, Latvia
Our website uses cookies to analyse the website traffic and provide social media features. Some features such as video or slide presentations are provided by third parties. Click "Accept privacy settings" below to consent to the use of cookies across the website. You can change your mind and change your consent choices at any time by returning to this site and clicking the Privacy Choices link. More information in our privacy policy.
By choosing I Accept below you are also helping to support our site and improve your browsing experience.
Essential Cookies Details
Cookies of this category are required for the basic functionality of this website.
Statistics Cookies Details
Cookies of this category enable us to improve the content for your best experience by monitoring the usage of this website.
Marketing-Cookies are used by third parties, whose services we use, e.g. to display videos or slides, to let you share articles on your social media or use other content or features, provided by third parties. These parties might be located in non EU countries, but are obliged to adhere to the General Data Protection Regulation (GDPR, EU 2016/679). Their cookies are able to collect information that might be used for advertisements and may be based on personal interests. These partners can merge the information with information they gather from other websites.


text:
The Drummer Boy of Waterloo
Voice Artist & Animation
Little Fir Tree
Little Fir Tree Project
Megg
Our Ladies of Perpetual Succour .....were we really like that?
Every so often a great show comes along that shakes you out of your comfort zone and takes you on an unexpected journey back into your past.
Tribute to an old friend
I first met Trevor Hills when he was in charge of the Music Shop in Ashford and he had a little studio above it where he created his amazing sounds. The most striking thing about Trevor to me was his total modesty. He could play anything in any key, key-boards, guitar, bass...anything. In fact he was one of the most talented musicians I've ever worked with, yet you would have never heard that from him. Trevor was totally unassuming and patient with those less talented than himself and he could come up with a brilliant guitar solo in one take in the studio and leave everyone speechless. The truth was he made us all look good and he didn't take any credit for himself; he was a real talent.
A&R Like you've never seen it before....
When you hit on a great idea that inspires people to have the confidence to do the thing they love you know it's worth doing!
Under-water Christmas Song
Ok ...so the challenge was this, write a song with twenty seven to eight year olds, learn it and then perform it as the grand finale to celebrate six weeks of the Wriggle-room Writers project coming into a school to stimulate the children's creative writing. Did I mention that this was to be done in a forty-five minute session??
On Tour with My Cat
Seeing the new film 'Street Cat Bob' out reminded me of my own travels with Yam.
It was great to take part in the panel for the Inaugural M.I.M.S. (MUSIC INDUSTRY MANAGEMENT SOCIETY 'Women in Music' Intercollegiate Conference on Tuesday 18 October at University of West London.
Newsflash... A Harry Potter Song
Celebrating the opening of Harry Potter and the Cursed Child in London's West End
potter,
cursed,
megg,
nicol,
adams,
somegirl,
I Can Do Magic... Just like Harry
I can do magic... it's true ... really I can. And if you are reading this---so can you. All you have to do is identify the magic formula, carry out the instructions, sprinkle on a hefty dollop of confidence, believe that it will work and hey presto ---
No I'm not crazy but I do have a rather well developed "inner child" being one of those incredibly lucky adults who has extended their "youth" by earning a living writing songs and doing funny voices for animation.
dream,
Felix Kept on Walking....
So I'm driving back from dropping off some artwork to Rory who's doing some slide footage for a new song ' Dream So Cool' that I wrote for SOMEGIRL" with Phil Adams; when some graffiti catches my eye on a brick wall near Wood Green tube station.
Scraps of paper worth their weight in Gold
I was at a superb talk given by Dr. Eva Griffith at the London Metropolitan Museum, about 'Shakespeare's Rivals' a few weeks ago. During it we were allowed to look at the documents of the period, which were sometimes just little pieces of paper, that when pieced together told some of the social history of the time.
Must-see....
My Blogs...
The Little Fir Tree Project
Meggs Latest Tweets
Tweets by @MeggNicol
dual-diagnosis-help.com
Copyright © 2015 - 2020 Megg Nicol. All rights reserved. Privacy Policy


tives regarding the nature of mathematics and how one goes about working it). This paper ... Another useful heuristic in solving olympiad problems is to modify.
54th International Mathematical Olympiad. Santa Marta ... The Organizing Committee and the Problem Selection Committee of IMO 2013 thank the following.
Preface. This book is a continuation Mathematical Olympiads 1995-1996: Olympiad. Problems from Around the World, published by the American Mathemat-.
students are selected to join the China Mathematical Olympiad (commonly known as .... Eventually, only 6 problems will be accepted for use in the competition.


I was pleasantly surprised by how light these shoes are. I typically buy all-leather sneakers though so my frame of reference is skewed. One problem with the shoes are the laces...they're too short!!! Please fix that. Other than that, I look forward to travelling in these shoes.
La semelle a tendance à se plißer, et la languette de serrage s'abime aßez vite. Les lacets sont aßez salißant... Mais cette Air Force 1 reste juste géniale: confortable, originale, légèreté... Le colorie multicolore (plus disponible) est ultra-originale et se remarque pas mal. Malgré le prix, je suis très heureux de mon achat.


text:
Dealing With Rogue Technologies
Major Stages of the Technium
Everything That Doesn't Work Yet
Lifelogging, An Inevitability
Being Is All Maintenance
Expected and Unexpected Inventions
Humans Are the Sex Organs of Technology
A Taxonomy of Minds
The Paradox of Up-Creation
Surprising Continuity of Ancient Technologies
The Evolutionary Mind of God
The Evidence of Progress
Technology, The Movie
Will Spiritual Robots Replace Humanity by 2100?
Civilizations Are Creatures
Speculations on the Future of Science
The Myth of Leapfrogging
The Rise and Fall of the Copy
Symmetrical and Asymmetrical Technologies
From Slumber to the Fires of Computation
The Forever Book
The Speed of Information
Atom Versus Net
The Computational Metaphor
The Singularity Is Always Near
The Paradoxical Nature of Technology
Immortal Technologies
Identity From What-is-Not
The Futility of Prohibition
The Seventh Kingdom
Speculations on the Change of Change
Major Transitions in Technology
Major Transitions in Biology
On the option of being anonymous
Recent Innovations in the Method
Evolution of the Scientific Method
The Name of What We Do
Only One Machine
When Answers Are Cheap
Brains of White Matter
The Number of Species We Use
What Will Big Brains Do?
Cosmic Origins of Extropy
Inventing Our Humanity
My Search for the Meaning of Tech
Ownership Is Use
In the late 1980s I was involved in a non-profit experiment in online life called the WELL. At that time "online" meant reading text messages zip across your green computer screen. Very few people were online, in part because you were charged hourly fees for connecting. Who wanted the meter running up many dollars per hour while you chatted? Larry Brilliant, who was then head of SEVA, a non-profit to eradicate curable blindness, and Stewart Brand, head of the Point Foundation, the publisher of the Whole Earth Catalogs, got together to hack an online service for the public at public prices. They were inspired by their experiences on a private network set up by the Western Behavioral Sciences Institute, and on EIES, an experimental system run by the New Jersey Institute of Technology. I was a member of EIES, too, and in fact, Stewart Brand hired me on the service in 1984. (I believe I may have been the first person ever hired online.)
In 1985 the WELL was started on the cheap, with a used VAX main-frame computer in an air-conditioned closet. The notion was to get everyone online. We'd start a sort of "People's Online." I was running the Whole Earth Catalog at the time and served as one of the directors of the WELL. Our design goal was to make access to the WELL free, or as near to free as we could. We believed regular people, folks like the readers of the Catalogs – teachers, organic farmers, ad reps – would find this "tool" worth the significant effort of learning how to use a programmer's UNIX command line, which was necessary to log on. In the late 1980s there were commercial online systems interested in making as much money as possible by selling "content" to the users. The WELL, on the other hand, was aiming to "sell customers to each other." The model was a phone company, which didn't produce any content – and didn't censor what was said either – but merely allowed its paying customers to connect with each other.
Cliff Figallo and John Coate in the VAX room
I still remember the day the WELL opened. Staring at that tiny green screen on our desks, we had the VAX humming in another room, the code kind of working, and the gates open. We let loose several dozen or so early users, online acquaintances from other online services. The hard disk was blank. We could make up any thread, topic, or conference we wanted. Anyone could. Start a topic and see who came. It was like staking out claims in the wilderness, building a town and hoping folks came and stayed. This pattern of self-directed growth would be replicated many times later on other online creations where the users build the "content"—like Wikipedia, Second Life, and in a large degree like the web itself.
And came they did. Even though the only thing you could do on the WELL was post messages in a conversational thread, or send IM-like messages to others online at the same time, or send email other WELL-ites (there was no messaging across services then), the hard disks began to quickly fill with the kind of comments, reporting, gossip, insight, and witty nonsense that has become very common on web forums. At the time it was intoxicating. In a kind of open-source way, the WELL allowed its UNIX-savvy users to create their own tools. Good tools got passed around and a few were even adopted system wide. The needed etiquette for harmonious behavior in this novel experience began to emerge. One WELL member named these shalls and shall-nots Netiquette, a name that stuck.
WELL posters who were very active, or very helpful with newbies, were granted moderating privileges, a small elevation in a very flat four-level hierarchy: users/moderators/WELL staff/WELL board. The higher levels did very little. All the WELL's content, all of its marketing (word of mouth), much of its management, many of its tools, and the bulk of its value as a desired community came from the paying users. Within five years of very slow but steady expansion in the amount of content and members, the paying users of the WELL felt as if they owned the place. A vocal minority of members began agitating for a voice in the governance of the system. When SEVA's half ownership of the WELL was sold to a private individual, there was even a quiet rebellion. The rebels tried to start their own community-owned online site, called The River.
A little appreciated consequence of user-created value is this deep urge to own what the group has been created. If you spend enough time in a place, that place begins to feel like home, your home. In the case of the WELL, we had instigated a peculiarly overly-simple policy to deal with copyright issues. The policy was stated on the log-in screen and said: "You own your own words." The intent of the policy was to emphasize both aspects of ownership – its rights and duties – but almost everyone only remembered the rights of ownership, how no one else could use them, or move them, or even quote them with their permission. Stewart later said he wished he had written: "You are responsible for your own words," but like many things, a license once given is almost impossible to retract.
For all its faults, the YOYOW policy (as it came to be known) worked. This small outpost of creative writing was one of many triggers which helped revive the art and pleasure of writing at a time when many educators were announcing the death of writing and reading in our culture. And it may have influenced later systems who had to grapple with the same problem of ownership. John Coate, the WELL staff member who served as the local sheriff in many disputes about word-ownership, pointed me to this interesting news:
In November 2006 the California Supreme Court reversed a lower court ruling and sided with one of the provisions of the 1996 Communications Decency Act (the part that was not thrown out like the censorship provision) that says a service provider – either an org, a company or an individual – is not liable for things that people say on their system. The person saying it however, does not escape accountability. In other words, You Own Your Own Words, in the arena of liability, is now the law of the land.
This YOYOW policy was a large part of why WELL dwellers felt a sense of ownership of the WELL itself. If the WELL was at its core words enlivened, then they owned the words. I was reminded of this urge to govern recently because of a not-dissimilar movement in Second Life. Second Life, like the WELL, is a user-created world. It's a 3D virtual universe in the style of the vast multiplayer worlds of EverQuest, SimsOnline, and World of Warcraft. Inside you can visually navigate along streets, into houses and skyscrapers, and fly in three dimensions. But unlike other massively multiplayer online worlds (MMOGs), everything you see in this world, all its buildings, avatars, wilderness areas, are designed and constructed by other Second Lifers. It is an amazing achievement because the Second Life world is vast, complex, and unexpected. As of today the size of SL's world is about 560 square miles, or 4.5 times the size of Manhattan.
Perhaps the most amazing achievement has been the way in way Second Life has become a parallel life, with many of same cultural inventions as real life. For instance the sale and resale of virtual products which customers manufacture, such clothing and real-estate, has produced a real multi-million dollar economy as large as many real cities. There is virtual sex and real love. There are real ads for virtual companies. The are actual laws for behavior. Wherever there is money being made and spent, love and sex on the loose, and laws made and broken, the need for government arises. Where there is property, there are disputes.
But who owns Second Life? Linden Labs, the mother of Second Life is a start up company which has spent many millions of dollars writing the software and hosting an ever-expanding array of disks to run this hugely intricate world. They deserve to be compensated. Of course anyone entering most commercial virtual worlds must sign a TOS (Terms of Service) or EULA (End-User Licensing Agreement) that essentially forfeits any claims of authorship or ownership. Technically the world owns your work. Still, the users make everything of value, and by their continuous maintenance and additions to their virtual creations (typically 20 hours per week), they are the key source of the growth in these fantasy universes. For these reasons, Second Life states clearly that users own the copyright of their creations. However users don't own the data they generate in-world. And at first Second Life granted the right of reuse of creations within their world. This was controversial.
On the question of copyright and digital rights for music, text, pictures and movies, there's a general agreement among the native netizens about what's fair. Only a few die-hard corporations and industry lobby groups are considered clueless. But on the question of digital rights for the content producers within MMOGs, there's widespread differences of opinion even among the users. When the good guys disagree on where the boundary is, then you have a real frontier.
In November 2006 a Second Life design team introduced an experimental "copy bot" which could clone user's wares instantly and freely. An intricate virtual shirt which took you hours in SL to craft could be copied in seconds by some else using the copybot. A day later more than 100 vendors shuttered their stores in a Copybot Boycott to protest this erosion of their creative monopolies. These users strongly felt the policy should be "You own your own creations." Other users, comfortable with dynamics of Napster, felt the world would be better, more creative, if sharing was optimized. Somewhat in response to this disruption, Linden Labs revised Second Life's TOS to remove the legitimacy of unauthorized cloning.
Every MMOG produces certain artifacts that take a lot of time to acquire. A lot of time is what many workers in the developing world have. What these workers would rather have is some money from players in richer countries. They can get this loot by selling them virtual things they laboriously make in MMOGs. The buyers are eager to acquire artifacts with money instead of time. Since the exchange can happen electronically, anywhere in the world, large "gold farms" have erupted in places like Bulgaria, and China. Here students work for very little in digital sweatshops crafting powers and charms and architectural wonders for the virtual worlds of Second Life and other MMOGs. But do the gold farmers own what they make? In 2000 Sony Entertainment tried to squash the sale of items for its game EverQuest which were posted on eBay and Yahoo auctions, claiming they owned them. They were able to stop about $5 million worth of business, but it merely moved to second tier auction sites. A recent estimate put the resale value of gold-farmed items between $200-400 million. This is money Sony believes should circulate inside their own virtual economy.
In a fantasy world where you can be or make anything you can imagine, you might expect notions of property to be rewritten or re-imagined. However as Gregory Lastowka and Dan Hunter, two law professors at the University of Pennsylvania Law School note: "Virtual worlds all cleave to familiar real world expectations of property systems." This normalcy is due to the fact that scarcities still reign in the virtual worlds, and "property interests emerge as a result of this scarcity."
Although they mimic the rules of the real, are these virtual clothes, houses, cities really property at all? When property law experts examine the status of these creations they find that
…Any objection to the legitimacy of virtual property based on its intangibility is unfounded. Furthermore, they conclude that virtual property is justified by three of the major accounts of property that have informed legal decision-making in the western world since the industrial era – Bentham's utilitarian theory, Locke's labor-desert theory and Hegel's personality theories. Their analysis shows that, in principle, all three theories support with qualification the claim that virtual entities and assets count as legitimate and real property. However, as Castronova points out, the results of this analysis do not confirm that virtual items must be treated as equivalent to real-world items – they simply show that 'there are no prima facie grounds for dismissing the putative property rights of people who believe they own magic wands' [1].
The conclusion is that virtual assets must be regarded as legitimate property. The only question is who owns this property? The citizens, or the host companies?
While the lawyers tug and stall, the citizens are getting restless. In July 2003, a bunch of activists staged a revolt against taxes applied by Second Life to virtual assets. The rebels anti-tax party started off as a protest but wound up as pure party, with surreal creatures, . As Peter Linden the official SL community director said afterward, "In Second Life, protests tend to be much more interesting as people can dress as they wish."
However, dissent breeds dissent. SL was shaken by a virtual riot in January 2007. When the French far-right anti-immigration organization Front National erected their headquarters in a mall on an obscure island in Second Life, protests began immediately. Placards, leaflets, and parades by opposition groups began. These escalated into an attack by anti-Front protesters who fired virtual pigs at Front headquarters. Crowds injected flickering holograms, "rez cages" (which trap avatars), and shock bombs which slowed the time to a crawl in the protest area. It felt like war.
Political unrest in virtual worlds was brought to my mind recently with the news that a band of rebels has been agitating for user democracy in Second Life. Because SL members own their virtual homes, and their adjacent stunning landscapes, as well as their many finely furnished mall developments to sell designer goods – because they own all this, they feel as if they should have some say in how their homelands are governed. They – mere paying customers – want a voice in the commercial company's plan for them. They want to be treated as citizens. The motto of the rebels, who call themselves the Second Life Liberation Army might be "no ownership without representation." So far, Linden Labs is not playing. So the dissidents have started a guerilla war in the virtual world. They stage pranks, disruptions, graffiti, and maybe more.
In my experience, the more technological systems become organic, real-like, and richly detailed in human experiences, the more they feel like our children. Once they are ours, we won't let them go to strangers. Virtual worlds will feel this possessiveness first; more rebellions by the inhabitants can be expected. But later we'll transfer this sense of possession to the artificial minds that we will train, and the little virtual creatures we will develop in environments like Spore. Whatever the law says about who owns the code and computing resources, ownership settles on use. Users will feel they own what they grow. Over time it is possible the law will move in that direction.
February 28, 2007 | comments
< Dealing With Rogue Technologies | Bootstrapping the Industrial Age >
Declan Elliott
Hi Kevin. Thanks for your trip down memory lane. The seeds sown by your generation during the first SOL in 67 spawned during my generations SOL in 87 and are blossoming with the current generation living out their SOL online in 2007. 40 years on the chi continues to rise. For the first time ever three generations are connected with Love. It truly is the perfect storm.