<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Juansecu</title>
    <description>The latest articles on DEV Community by Juansecu (@juansecu).</description>
    <link>https://dev.to/juansecu</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F312396%2Fd3ced60c-8ff6-4e2f-92b2-9caa16b3d74b.png</url>
      <title>DEV Community: Juansecu</title>
      <link>https://dev.to/juansecu</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/juansecu"/>
    <language>en</language>
    <item>
      <title>Did you know Docker images of Node.js running on Alpine Linux are "unofficial"?</title>
      <dc:creator>Juansecu</dc:creator>
      <pubDate>Tue, 19 May 2026 22:41:50 +0000</pubDate>
      <link>https://dev.to/jscv-solutions/did-you-know-docker-images-of-nodejs-running-on-alpine-linux-are-unofficial-4anm</link>
      <guid>https://dev.to/jscv-solutions/did-you-know-docker-images-of-nodejs-running-on-alpine-linux-are-unofficial-4anm</guid>
      <description>&lt;h2&gt;
  
  
  Table of Contents
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;What does it mean by Docker images of Node.js running on Alpine Linux are "unofficial"&lt;/li&gt;
&lt;li&gt;Why does the Node.js team deliver Alpine Linux images as official without properly testing them?&lt;/li&gt;
&lt;li&gt;Since Alpine Linux images are "unofficial", should I stop using them in production environments?&lt;/li&gt;
&lt;li&gt;References&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;Yes, you heard it right!&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;DOCKER IMAGES OF NODE.JS RUNNING ON ALPINE LINUX ARE "UNOFFICIAL"!&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;At least, this is how the Node.js team refers to them when it comes to support!&lt;/p&gt;

&lt;p&gt;The reason? They don't actively test Alpine Linux builds! At least not in their CI/CD environments! This is because &lt;strong&gt;Alpine Linux builds are in experimental status&lt;/strong&gt;!&lt;/p&gt;




&lt;p&gt;At this point, you may be asking: &lt;strong&gt;Why does the Node.js team deliver Alpine Linux images as official without properly testing them?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;To be honest, I may not have all the answers on this matter, because, though I use Node.js in my day-to-day, I'm not involved in the development of Node.js (not on a deep level, at least). Although I'm here to bring you a bit of information on this matter while trying to answer some questions you may have on the subject.&lt;/p&gt;




&lt;h2&gt;
  
  
  What does it mean by Docker images of Node.js running on Alpine Linux are "unofficial"?
&lt;/h2&gt;

&lt;p&gt;As I said before, the Node.js team doesn't actively test Node.js builds in Alpine Linux environments (at least not in their CI/CD environments). Therefore, the support they can provide for running Node.js applications on Alpine Linux is highly limited.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why does the Node.js team deliver Alpine Linux images as "official" without properly testing them?
&lt;/h2&gt;

&lt;p&gt;Apart from the fact that the build and delivery process of Docker images of Node.js running on Alpine Linux is made through &lt;a href="https://github.com/nodejs/docker-node" rel="noopener noreferrer"&gt;the same CI/CD workflows that &lt;/a&gt;, I can only guess they do it because Alpine Linux is widely used by applications used in production environments due to its small size and resource usage.&lt;/p&gt;

&lt;h2&gt;
  
  
  Since Alpine Linux images are "unofficial", should I stop using them in production environments?
&lt;/h2&gt;

&lt;p&gt;Not at all. At least, I don't think so. Especially because &lt;a href="https://github.com/nodejs/node/issues/62764" rel="noopener noreferrer"&gt;the Node.js team is looking for some people from the community to help to solve issues related to running Node.js on Alpine Linux&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;If you are interested in helping the Node.js team to actively find and solve issues running Node.js on Alpine Linux, I personally encourage you to &lt;a href="https://github.com/nodejs/node/issues/62764" rel="noopener noreferrer"&gt;get to the issue talking on this matter&lt;/a&gt; and show them your interest in helping them!&lt;/p&gt;




&lt;h2&gt;
  
  
  References
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://github.com/nodejs/node/issues/62764" rel="noopener noreferrer"&gt;Promote Alpine Linux out of experimental to be a tier 2 platform&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/nodejs/docker-node" rel="noopener noreferrer"&gt;Official Node.js Docker image repository&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>node</category>
      <category>javascript</category>
      <category>linux</category>
      <category>docker</category>
    </item>
    <item>
      <title>RTMP Server Development with Red5 Server Series: Capturing RTMP Traffic with Wireshark</title>
      <dc:creator>Juansecu</dc:creator>
      <pubDate>Tue, 04 Apr 2023 20:53:25 +0000</pubDate>
      <link>https://dev.to/juansecu/rtmp-server-development-with-red5-server-series-capturing-rtmp-traffic-with-wireshark-31me</link>
      <guid>https://dev.to/juansecu/rtmp-server-development-with-red5-server-series-capturing-rtmp-traffic-with-wireshark-31me</guid>
      <description>&lt;p&gt;When you're developing any non-http application, it's necessary to capture traffic (in most cases) with a capture traffic tool like Wireshark, and if you're developing a RTMP server for an old Flash application, then you will find very useful tools of this type.&lt;/p&gt;

&lt;h2&gt;
  
  
  Understanding how to use Wireshark to capture RTMP traffic
&lt;/h2&gt;

&lt;p&gt;When I started to use Wireshark to record RTMP traffic, I found some useful information to capture RTMP traffic using Wireshark.&lt;/p&gt;

&lt;p&gt;First, I found that usually, RTMP (Real-Time Messaging Protocol) is based on TCP (Datagram Delivery Protocol) as its transport protocol, which in most cases, uses Ethernet as its transport protocol. This information can be found in the &lt;a href="https://wiki.wireshark.org/" rel="noopener noreferrer"&gt;Wireshark's wiki&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Second, when I tried to capture RTMP traffic using the previous information in a Windows 11 device, I got a error message from Npcap like this:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Flcsiwv2fqiw1lhxg4h2p.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Flcsiwv2fqiw1lhxg4h2p.png" alt="Npcap Error in Windows 11" width="503" height="195"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;This is when, while trying to find a fix for this error message on Internet, I found &lt;a href="https://github.com/nmap/npcap/issues/628" rel="noopener noreferrer"&gt;this issue in the official Npcap repository&lt;/a&gt;, which specifies this error message when using Wireshark in Windows 11 devices.&lt;/p&gt;

&lt;p&gt;Moving forward in the issue's conversation, I reached &lt;a href="https://github.com/nmap/npcap/issues/628#issuecomment-1283568880" rel="noopener noreferrer"&gt;this comment&lt;/a&gt;, which describes that this issue is fixed when using Npcap 1.60 instead of lasts versions.&lt;/p&gt;

&lt;h2&gt;
  
  
  References
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;&lt;a href="https://en.wikipedia.org/wiki/Real-Time_Messaging_Protocol" rel="noopener noreferrer"&gt;Real-Time Messaging Protocol (RTMP)&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href="https://en.wikipedia.org/wiki/Transmission_Control_Protocol" rel="noopener noreferrer"&gt;Transmission Control Protocol (TCP)&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href="https://github.com/nmap/npcap/issues/628#issuecomment-1283568880" rel="noopener noreferrer"&gt;Using Npcap 1.60 to capture RTMP traffic in Windows 11&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

</description>
    </item>
  </channel>
</rss>
