DanRegalia

Just a quick question on the draw.io. I'm trying to set it up, but everytime I hit install (new app store, on 6.9.2). I show Draw.io, Network type Bridge, Shell command is Shell. Webui port is 3000, basically leaving it all as is. It's not working... I hit apply/done and it goes right back to the left side flyout install again asking me to install. I'm 100% sure it's me. Do I need to give it a new IP address, or it's own internal IP address? Pardon my stupidity if that's the case... but I'm guessing I would give it a custom/br0 address and let it get assigned via dhcp. But then I only have apply and reset available... not done... I feel like I'm missing something big here. lol.

Can you send a screen shot where you're expecting to find it?

You set it up when you install it and run it the first time

Hey wjs, without seeing the actual files, I can't help you out. But there are significant changes between Portainer and Portainer CE... Now, both of them are up here on the app store, so you can install Portainer on your unraid box, and see if the stacks still work there, and then check it inside of Portainer CE... Also, you have to make sure you're on the right version of Unraid, to make sure that the docker system supports your stack and functionality. Lastly, for what it's worth, you need to check out the portainer slack community if you can't get any questions answered. https://portainer.slack.com Hope some of these troubleshooting tips help you get to where you're going.

Just wanted to let you know the update came thru to 2.1.1 and here are the features: New Feature Highlights 1. Support for Compose v3.8 when deploying against standalone Docker Hosts This feature has been in demand for over a year, so we're excited for you to get your hands on it. We now ship the compose binary as part of the Portainer container. This means you can now use plain Compose files up to 3.8 (or higher for standalone) to deploy stuff through the UI/API. Note this feature is only available for AMD64 architectures (Windows & Linux). The team are still working on creating a standalone binary for Compose that works on ARM/ARM64 (we aim to add support for these architectures in a future release). 2. Support for Compose v3.8 when deploying against Swarm Hosts Another feature that has been in hot demand! This one was a challenge, but you can now deploy any Compose v3.8 stack against Swarm. 3. Portainer Images now built with Docker Buildx We needed to report our images to Buildx to get native support for all architectures, and importantly, to provide Windows images spanning 1809-2004. This was also needed in order to get Portainer working on Docker 20.04.x on platforms other than AMD64. 4. De-emphasis the Portainer Login box when OAuth is used When you have OAuth authentication enabled, the Portainer login screen becomes somewhat pointless, as you don’t need to enter creds, instead you need to click a “login with OAuth” button; so we have now hidden the login screen and just show the “login with OAuth” button. 5. Advanced Deployment for Kubernetes We already allowed admins to deploy Kubernetes apps using a manifest directly within Portainer, we have now expanded this to allow the creation of any Kubernetes resource.

Apache NiFi supports powerful and scalable directed graphs of data routing, transformation, and system mediation logic. Some of the high-level capabilities and objectives of Apache NiFi include: Web-based user interface Seamless experience between design, control, feedback, and monitoring Highly configurable Loss tolerant vs guaranteed delivery Low latency vs high throughput Dynamic prioritization Flow can be modified at runtime Back pressure Data Provenance Track dataflow from beginning to end Designed for extension Build your own processors and more Enables rapid development and effective testing Secure SSL, SSH, HTTPS, encrypted content, etc... Multi-tenant authorization and internal authorization/policy management http://nifi.apache.org/ Let me know if you find any issues with the install. It's fairly straight forward.

@toasti, Thanks so much for the ping back, and appreciate the heads up.

Second on the 'cannot communicate with the server'. Last time we changed the network type to e1000-82545em per this post here However the xml is correct on this for the new version, but it is still not working. Any guidance would be awesome. Thanks!

So, kind of a weird error... This one says access is denied? I have Catalina and Mojave both installed...But this just isn't working. I looked in my iso folder, and I see the big sur image downloaded, or at least 2GB of it. Thoughts or ideas? BTW, using method 2. Method 1 seems to just stop. 2020-12-09 18:53:44,444 Network Request: Fetching https://swscan.apple.com/content/catalogs/others/index-10.16-10.15-10.14-10.13-10.12-10.11-10.10-10.9-mountainlion-lion-snowleopard-leopard.merged-1.sucatalog 2020-12-09 18:53:45,436 Selected macOS Product: 001-83532 /Macinabox/unraid.sh: line 273: /Macinabox/tools/FetchMacOS/BaseSystem/SharedSupport.dmg: Permission denied

This is the support thread for the Portainer-CE image. Currently tweaking it for Unraid, but it's available now. This will be the support post. Can one of the Mods move this over to the other forum? Thanks.