投稿時間:2023-05-08 14:14:50 RSSフィード2023-05-08 14:00 分まとめ(17件)

カテゴリー等	サイト名等	記事タイトル・トレンドワード等	リンクURL	頻出ワード・要約等/検索ボリューム	登録日
IT	ITmedia 総合記事一覧	[ITmedia PC USER] サンワ、2台まで同時に使えるBluetoothスピーカーフォン	https://www.itmedia.co.jp/pcuser/articles/2305/08/news089.html	bluetooth	2023-05-08 13:50:00
IT	ITmedia 総合記事一覧	[ITmedia Mobile] 最大150型投影のポータブルプロジェクター「GeePro Auto」発売　14センチの立方体で1万9800円	https://www.itmedia.co.jp/mobile/articles/2305/08/news087.html	geeproauto	2023-05-08 13:23:00
IT	ITmedia 総合記事一覧	[ITmedia ビジネスオンライン] 職場でのマスクはどうする？　5類移行で「出社が増える」	https://www.itmedia.co.jp/business/articles/2305/08/news082.html	itmedia	2023-05-08 13:05:00
IT	情報システムリーダーのためのIT情報専門サイト IT Leaders	米オラクル、Oracle Fusion Applicationsを強化、AIでリードタイムの予測精度を向上 | IT Leaders	https://it.impress.co.jp/articles/-/24787	itleaders	2023-05-08 13:35:00
AWS	lambdaタグが付けられた新着投稿 - Qiita	CDK(ver.2) pythonでlambdaとRDSをproxyで繋いでみた	https://qiita.com/rm0063vpedc15/items/2834b4213ac0b0bd5ce9	awscdk	2023-05-08 13:29:16
AWS	AWSタグが付けられた新着投稿 - Qiita	CDK(ver.2) pythonでlambdaとRDSをproxyで繋いでみた	https://qiita.com/rm0063vpedc15/items/2834b4213ac0b0bd5ce9	awscdk	2023-05-08 13:29:16
海外TECH	DEV Community	Docker Networking: A Step-by-Step Guide for Developers	https://dev.to/rwiteshbera/docker-networking-a-step-by-step-guide-for-developers-2d27	Docker Networking A Step by Step Guide for Developers Overview of DockerDocker is a platform that allows developers to package and run applications in an isolated environment called a container Docker has become a popular tool among developers for its ability in application deployment and management However networking can be a complex topic when it comes to Docker especially for beginners In this guide we will provide a step by step overview of Docker networking including the Container Networking Model network drivers and practical examples Networking is about establishing connections transferring data and exchanging information between nodes Similarly Docker networking involves making connections between containers and external systems through the host machine while the Docker engine is working Container Networking ModelContainer network model is a standard proposed by Docker that provides a well defined interface or API that helps in establishing connections between containers and network plugins Libnetwork is the native Go implementation of the CNM for connecting containers It provides an interface between the Docker engine and network drivers It is built on main components Sandbox Endpoint NetworkSandbox A sandbox contains the configuration of the container s network This includes routing DNS settings and endpoints for multiple networks Endpoint Offers connectivity for services provided by the container It links a sandbox to a network Network Provides connectivity between a group of endpoints belonging to the same network It isolates them from the rest of the system Apart from these there has more objects Network Controller and Driver Network Controller This serves as the entry point into libnetwork offering simple APIs for users Driver responsible for managing the network Drivers can be both inbuilt and remote provided by rd party plugin to satisfy different use cases and scenarios Network DriversDocker supports different types of network drivers for certain use cases Those are Bridge Network The private default network driver is automatically created by Docker on the host Host Network Using this network you can eliminate the isolation between the container and the host allowing you to directly use the host IP However you will be unable to run multiple web containers on the same host using the same port Overlay Network connects multiple Docker engines together and enables swarm services to communicate with each other IPvlan Network allows you to create a completely new virtual network inside your Docker host IPv and IPv can be controlled by these networks Macvlan Network assigns a MAC address to a container treating the container as a physical device on your network none You can completely disable the networking service of a container Let s do some hands on Open your terminal and list all the current networks before doing anything docker network lsNETWORK ID NAME DRIVER SCOPEbffcae bridge bridge localefbbf host host localedbaeae none null localThere are three network listed bridge host and none Every network has its own id Bridge is the default and most common network This network is easy to manage Whenever you run a container if you don t mention any network configuration Docker engine automatically assigns bridge network to it Let s say you run a container from nginx image Now inspect the network of the container by docker inspect lt container name id gt docker run d it name alpine alpine latest fdfadadebbebbddefae docker run d it name alpine alpine latest ddeafaafbacbffdadfdfbddeabdccfdc docker inspect alpineYou will get lots of info about the container and search Networks Networks bridge IPAMConfig null Links null Aliases null NetworkID bffcaecaeedcbceccfcabadcdbcecdab EndpointID deebdaefecfafcdedebffeacdc Gateway IPAddress IPPrefixLen IPvGateway GlobalIPvAddress GlobalIPvPrefixLen MacAddress ac DriverOpts null You will get it where the bridge is mentioned and all the network details are given Get the IP address assigned to the container docker inspect alpine grep IPAddress SecondaryIPAddresses null IPAddress IPAddress See what containers are connected with the bridge network Name bridge Id bffcaecaeedcbceccfcabadcdbcecdab Created T Z Scope local Driver bridge EnableIPv false IPAM Driver default Options null Config Subnet Gateway Internal false Attachable false Ingress false ConfigFrom Network ConfigOnly false Containers ddeafaafbacbffdadfdfbddeabdccfdc Name alpine EndpointID dbdbefdeebcccdeafedbceecbbffd MacAddress ac IPvAddress IPvAddress fdfadadebbebbddefae Name alpine EndpointID deebdaefecfafcdedebffeacdc MacAddress ac IPvAddress IPvAddress Options com docker network bridge default bridge true com docker network bridge enable icc true com docker network bridge enable ip masquerade true com docker network bridge host binding ipv com docker network bridge name docker com docker network driver mtu Labels Under the Containers key connected containers are listed along with information about their IP addresses See the IP address of the network driver easily ip a grep docker docker lt NO CARRIER BROADCAST MULTICAST UP gt mtu qdisc noqueue state DOWN group default inet brd scope global dockerdocker is the name of default bridge network Now let s use the bash shell of alpine container using docker attach alpineUse ip addr show to see the IP address of the container docker attach alpine It will open the interactive mode of the container and now you can use bash commands inside the alpine Use ip addr show to see the IP address of the container ip addr show lo lt LOOPBACK UP LOWER UP gt mtu qdisc noqueue state UNKNOWN qlen link loopback brd inet scope host lo valid lft forever preferred lft forever tunl NONE lt NOARP gt mtu qdisc noop state DOWN qlen link ipip brd iptnl NONE lt NOARP gt mtu qdisc noop state DOWN qlen link tunnel brd eth if lt BROADCAST MULTICAST UP LOWER UP M DOWN gt mtu qdisc noqueue state UP link ether ac brd ff ff ff ff ff ff inet brd scope global eth valid lft forever preferred lft foreverIn the first line lo represents the loopback device which is a virtual network interface that allows your computer to communicate with itself This device is primarily used for diagnostics troubleshooting and connecting to servers running on the local machine tunl is an IPIP tunnel used for encapsulating pod traffic Ignore it now In the second last line inet is the IP address of the alpine container Now make sure you have an internet connection and let s ping Google s server in alpine interactive mode You can stop it by pressing shift ctrl c ping google comPING google com data bytes bytes from seq ttl time ms bytes from seq ttl time ms bytes from seq ttl time ms bytes from seq ttl time ms bytes from seq ttl time ms bytes from seq ttl time ms bytes from seq ttl time ms bytes from seq ttl time ms bytes from seq ttl time ms C google com ping statistics packets transmitted packets received packet lossround trip min avg max ms You can stop the ping by pressing shift ctrl c Now without typing exit you can stop and delete the containers docker container stop alpine alpinedocker container rm alpine alpine Custom or user defined networkTo create your own custom network all containers connected to this network can communicate with each other without exposing their ports to the outside world This results in improved isolation because all networks with the network option specified are attached to a bridge network How to create a user defined network docker network create driver bridge my bridge We can create our own bridge network by using the above command If you don t specify the driver option the command automatically creates a bridge network for you docker network ls NETWORK ID NAME DRIVER SCOPEbffcae bridge bridge localefbbf host host localbbbb my bridge bridge localedbaeae none null localYou can see a new my bridge the user defined network has been created with bridge driver Use inspect command to see the IP address assigned to the new network docker network inspect f json IPAM Config my bridge Subnet Gateway Now let s use netshoot a Docker image equipped with a set of networking troubleshooting tools that can be used for Docker networking Create two containers with the same netshoot image docker run d it name net rm network my bridge nicolaka netshoot bin bash docker run d it name net rm network my bridge nicolaka netshoot bin bashThe rm flag is used to instruct Docker Engine to clean up the container and remove the file system once the container exits It will open the container in an interactive mode as I have used it and also attach it to user defined network by using network my bridge Use ip a to check the IP address of the newly created container which is generated from my bridge making them quite similar docker attach net dbac ip a lo lt LOOPBACK UP LOWER UP gt mtu qdisc noqueue state UNKNOWN group default qlen link loopback brd inet scope host lo valid lft forever preferred lft forever tunl NONE lt NOARP gt mtu qdisc noop state DOWN group default qlen link ipip brd iptnl NONE lt NOARP gt mtu qdisc noop state DOWN group default qlen link tunnel brd permaddr eaf f bf eth if lt BROADCAST MULTICAST UP LOWER UP gt mtu qdisc noqueue state UP group default link ether ac brd ff ff ff ff ff ff link netnsid inet brd scope global eth valid lft forever preferred lft foreverNow let s ping another container net from net using the IP address of netYou can see that two containers can communicate with each other because they are on the same network my bridge Now let s use a new container with a different network docker network create my bridge dbeaccdabafbdcbadfdededbcdf docker run d it name net rm network my bridge nicolaka netshoot bin bashcacbebdedcecaadbdecbbcffbbceb docker attach net cacbeb ping PING bytes of data From the net container if we want to ping net using its IP address it will not work because they are both on different networks Refer to the image below Host NetworkAs the name suggests host drivers utilize the networking provided by the host machine This removes network isolation between the container and the host machine where Docker is running For instance if you run a container that binds to port and uses host networking the container s application becomes accessible on port via the host s IP address With this configuration you cannot run multiple web containers on the same host using the same port as the port is now shared among all containers within the host network To use host network docker run d name webhost network host nginx latestThere is no need to expose the port now as the container utilizes the host network allowing you to access Nginx on port Now Stop the Nginx container docker stop webhost Macvlan and IPvland NetworkMacvlan and IPvlan are used in Docker networking to assign a unique MAC and IP address to each container allowing them to communicate directly with the physical network connected to the Docker host You might want to use Macvlan or IPvlan when running a container that requires a service such as DNS or DHCP but the host already has a DNS or DHCP server running In such a scenario using a bridge network and exposing the service to a different external port may not work for standardized protocols like DNS or DHCP since clients expect them to operate on specific ports Macvlan NetworkMacvlan is a way to connect Docker containers directly to the physical network which can be useful for certain types of applications It assigns a unique MAC address to each container s virtual network interface making it look like a physical interface To create a Macvlan network you need to use drive macvlan and specify the subnet and gateway of the host machine This will create a virtual network interface for the container with a unique MAC address that s connected directly to the physical network wlo is a network interface name representing a wireless network interface on a computer In this instance it has been assigned an IP address of with a subnet mask of This IP address is likely assigned dynamically scope global dynamic by a DHCP server on the local network docker network create d macvlan subnet gateway o parent eth macnetWhen using a macvlan network you can exclude specific IP addresses from being assigned to containers in the network This can be useful if an IP address is already in use and you want to prevent it from being assigned to a container To achieve this you can use the aux addresses option to specify the IP addresses to exclude docker network create d macvlan subnet gateway aux addresses my macvlan o parent eth macnet IPvlan Networkipvlan is a type of Docker network driver that allows you to create multiple virtual networks on a single physical interface Each virtual network operates as a separate layer domain docker network create d ipvlan subnet subnet gateway gateway o parent eth ipnet Difference between macvlan and ipvlanmacvlan and ipvlan are two ways to create virtual networks inside a computer which can allow multiple containers to communicate with each other and with the outside world macvlan creates virtual network interfaces that connect directly to the physical network They possess their own MAC addresses and can be detected by other devices on the network This is beneficial in situations where containers need to communicate directly with the physical network such as with a router or a DHCP server On the other hand ipvlan creates virtual network interfaces that share the same MAC address as the physical network interface which means they are less visible on the network This can be useful when you want to isolate containers from the physical network or when you need to give a container multiple IP addresses In simple terms macvlan is beneficial when you need containers to communicate directly with the physical network whereas ipvlan is advantageous when you want to maintain separation between containers and the physical network or when a container requires multiple IP addresses In two separate terminals create two separate containers on ipvlan and they communicate with each other docker run it name net network ipnet nicolaka netshoot bin bash docker run it name net network ipnet nicolaka netshoot bin bash Overlay NetworkWhen using the overlay network driver in Docker you can create a distributed network that spans across multiple Docker hosts This network is created on top of the individual host specific networks and allows containers to communicate securely with each other even when encryption is enabled Docker handles the routing of each packet to the correct Docker daemon host and the correct destination container An overlay network called ingress handles the control and data traffic related to swarm services You can learn more about it by visiting Disable networking for a containerIf you wish to entirely disable the networking stack for a container you can utilize the network none flag when initiating the container Inside the container only the loopback device will be created Consider the following example ConclusionIn conclusion Docker provides an efficient way to package and run applications in an isolated environment using containers Its networking capabilities allow for establishing connections between containers and external systems through the host machine while the Docker engine is working The Container Networking Model provides a well defined interface for connecting containers and Docker supports different types of network drivers for specific use cases Overall Docker is a powerful tool for developers to streamline their application deployment process Subscribe to my newsletter for more content like this If you enjoyed reading this article please consider sharing it with your colleagues and friends on social media Additionally you can follow me on Twitter for more updates on technology and coding Thank you for reading	2023-05-08 04:30:00
金融	生命保険協会	生命保険契約者で被災された方への特別取扱いについて（石川県）	https://www.seiho.or.jp/info/news/2023/post_2.html	生命保険	2023-05-08 13:28:43
海外ニュース	Japan Times latest articles	Signs of healing grow in Japanese baseball’s attendance figures	https://www.japantimes.co.jp/sports/2023/05/08/baseball/japanese-baseball/sac-bunts-marines-hawks/	Signs of healing grow in Japanese baseball s attendance figuresThe relaxation of COVID rules and the excitement of the World Baseball Classic created the perfect storm to help NPB step back into the light	2023-05-08 13:24:29
海外ニュース	Japan Times latest articles	Furuhashi nets 30th goal as Celtic seal Scottish title	https://www.japantimes.co.jp/sports/2023/05/08/soccer/furuhashi-celtic-score/	Furuhashi nets th goal as Celtic seal Scottish titleThe milestone follows the disappointment of being left out of Japan s World Cup squad which Furuhashi has turned into a source of motivation	2023-05-08 13:18:01
マーケティング	MarkeZine	AOSデータ、広告データの保存管理を行うプラットフォームの提供を開始　AI活用にも対応	http://markezine.jp/article/detail/41972	開始	2023-05-08 13:30:00
IT	週刊アスキー	Switch／Xbox One版『MELTY BLOOD: TL』が40％オフセールを実施中	https://weekly.ascii.jp/elem/000/004/135/4135617/	meltybloodtl	2023-05-08 13:50:00
IT	週刊アスキー	母の日にコース料理とケーキで感謝の気持ちを伝えよう！　キンプトン新宿東京、「母の日お祝いプラン」を5月14日まで販売	https://weekly.ascii.jp/elem/000/004/135/4135580/	期間限定	2023-05-08 13:45:00
IT	週刊アスキー	6月12日深夜2時から！「Xbox Games Showcase」＆「Starfield Direct」が放送決定	https://weekly.ascii.jp/elem/000/004/135/4135608/	日本時間	2023-05-08 13:30:00
IT	週刊アスキー	吉野家、から揚げ関連商品が10％の「から揚げ祭」開催 店内飲食・テイクアウトが対象	https://weekly.ascii.jp/elem/000/004/135/4135614/	飲食	2023-05-08 13:30:00
IT	週刊アスキー	おひとり様ピザ＋サイドメニュー2品がお買い得！ ドミノ・ピザ「お財布救済！マイドミノランチウィーク」	https://weekly.ascii.jp/elem/000/004/135/4135612/	mydominos	2023-05-08 13:20:00
マーケティング	AdverTimes	電通デジタル、ISID、イグニション・ポイントが人的資本経営支援のソリューションの提供を開始	https://www.advertimes.com/20230508/article418382/	humanalytics	2023-05-08 04:36:20