@chet1 wrote:
I've been following this blog about a 9300 hosting a Minecraft docker container. I'm trying this as a guide to add in my own containers.
https://blogs.cisco.com/developer/minecraft-on-catalyst-switch#comments
Now, I don't have Cisco DNA Center and have been researching and doing this via command line. I've copied the 'run-opts' and the settings as far as I can tell, yet when the container starts, it'll be Running for a few seconds then hit a Stopped state. I can not for the life of me figure out why it stops. Any help resolving this is greatly appreciated.
Switch: C9300-48U
Software version: 17.02.01
Show run of app-hosting:
.
app-hosting appid minecraft
app-vnic AppGigabitEthernet trunk
guest-interface 2
vlan 300 guest-interface 0
guest-ipaddress 192.168.10.100 netmask 255.255.255.0
app-default-gateway 192.168.10.254 guest-interface 0
app-device usb-port 1 usb-port-label minecraft
app-resource docker
run-opts 1 "-e EULA=TRUE"
run-opts 2 "-e OVERRIDE_SERVER_PROPERTIES=true"
run-opts 3 "-e MOTD=Catalyst9300"
run-opts 4 "-p 25565:25565"
.
Show run of interface AppgigabitEthernet:
interface AppGigabitEthernet1/0/1
switchport trunk allowed vlan 300
switchport mode trunk
switchport app-interface
LAB-Switch#app-hosting start appid minecraft
minecraft started successfully
Current state is: RUNNING
LAB-Switch#show app-hosting list
App id State
---------------------------------------------------------
minecraft RUNNING
LAB-Switch#show app-hosting list
App id State
---------------------------------------------------------
minecraft STOPPED
I also have the same question and have been trying to understand what could cause a Docker container on a Cisco Catalyst switch to start successfully and then immediately move into a stopped state. The configuration looks like it should at least bring the container up, so I’m wondering if there is something being missed in the app-hosting settings, Docker image requirements, resource allocation, or logging that could explain why it shuts down after a few seconds. It would be really helpful if someone could share the troubleshooting steps they used when dealing with similar container lifecycle issues on the C9300 platform.
I’m also curious if there are any commands that can provide more detailed information about why the container stops, such as logs from the app-hosting environment or Docker process output. Sometimes containers fail because of missing environment variables, storage issues, insufficient CPU or memory, networking problems, or an application-level crash, but it’s not always obvious from the basic status output. I also have the same question and would appreciate any advice from someone who has successfully deployed Minecraft or other Docker containers directly on a Catalyst switch without DNA Center. A breakdown of the common checks and where to find the actual error message would be very useful.
