#docker

[grif-hawaiian-rolls]

sometimes u just get so filled w thoughts about a pair of characters u gotta just go bonkers ya know

[alpine-official]

i love being shoved into a tiny little docker container or a shitty RP2040 microcontroller :33 please use me in a shitty, tiny embedded system like the naughty little distro i am ><

[openmediavault-official]

openmediavault-compose is the cure

[nixcraft]

64 vCPU/256 GB ram/2 TB SSD EC2 instance with #FreeBSD or Debian Linux as OS 🔥

[docker-official]

Id like to thank @debian-official, if it wasnt for them this idea wouldnt have come to me.

What projects is everyone working on? Im curious and want to see what the IT community is bashing their heads against.

Ill start, I am setting up a personal website for my homelab! The site is through nginx. I dont have any experience with html or css or anything like that and for me its a fun little challenge. It has also allowed my to get my "cdn" going again which I am quite pleased about ^~^

[hayacode]

Hello everyone ✨

So as you know I have been applying for jobs for a few reasons ..

- I want to see what they want

- How interviews goes in my country

- What skills are important

And stuff like that, and now after I did that.. I want to start a new plan/goal (for 6 weeks or maybe more if I get a job)

1- Reviewing JavaScript

2- Back to study Python

3- Do practice every day for both of them

4- Learn how to use streamlit and make at least one project.

5- Practice my Bootstrap (my current workshop)

6- Learning about React (only basics info before my main workshop start on 22 July)

You may be wondering “why did I choose streamlit (that focused on data) even though there are much better skills to focus on as a frontend developer?”

The reason for that is, my dream job needs these.

And I plan to focus on them and apply for it 👩🏻‍💻

Worst case scenario is me never getting the job but at least I get the skills and practice.

Please wish me luck, and I will definitely update you on it later ✨

If you have any advice for me, please let me know. I love hearing your thoughts 🤍

Ps. I will not learn Docker because from what I saw. I can’t really learn it with small projects (which is what I mostly do, so I will leave it out for now)

[utopicwork]

This tool rules, it automatically converts docker start up commands into docker compose yml, used to waste a lot of time doing this manually

[gobusto]

Half Life running under WINE via a VNC connection to a Docker container running Alpine Linux

[jestandvex]

for all my computer science critters out there, "unfinished vidulch" sounds like the default name on a docker container

[jointhefediverse]

WE LOVE TO SEE IT! Friendica's official [virtual image] trending on Docker. 🥹🐳

(Not to excuse Home Assistant receiving the first spot. 🏡🎖️ It's a widely recognized and powerful open-source automation network for your smart-home. In competition with other integrated hub systems, notably Alexa or Google Assistant, aside from being FOSS: it's privacy-oriented and far more intuitive/extensive with its capabilities.)

[blubberquark]

Nothing encapsulates my misgivings with Docker as much as this recent story. I wanted to deploy a PyGame-CE game as a static executable, and that means compiling CPython and PyGame statically, and then linking the two together. To compile PyGame statically, I need to statically link it to SDL2, but because of SDL2 special features, the SDL2 code can be replaced with a different version at runtime.

I tried, and failed, to do this. I could compile a certain version of CPython, but some of the dependencies of the latest CPython gave me trouble. I could compile PyGame with a simple makefile, but it was more difficult with meson.

Instead of doing this by hand, I started to write a Dockerfile. It's just too easy to get this wrong otherwise, or at least not get it right in a reproducible fashion. Although everything I was doing was just statically compiled, and it should all have worked with a shell script, it didn't work with a shell script in practice, because cmake, meson, and autotools all leak bits and pieces of my host system into the final product. Some things, like libGL, should never be linked into or distributed with my executable.

I also thought that, if I was already working with static compilation, I could just link PyGame-CE against cosmopolitan libc, and have the SDL2 pieces replaced with a dynamically linked libSDL2 for the target platform.

I ran into some trouble. I asked for help online.

The first answer I got was "You should just use PyInstaller for deployment"

The second answer was "You should use Docker for application deployment. Just start with

FROM python:3.11

and go from there"

The others agreed. I couldn't get through to them.

It's the perfect example of Docker users seeing Docker as the solution for everything, even when I was already using Docker (actually Podman).

I think in the long run, Docker has already caused, and will continue to cause, these problems:

Over-reliance on containerisation is slowly making build processes, dependencies, and deployment more brittle than necessary, because it still works in Docker

Over-reliance on containerisation is making the actual build process outside of a container or even in a container based on a different image more painful, as well as multi-stage build processes when dependencies want to be built in their own containers

Container specifications usually don't even take advantage of a known static build environment, for example by hard-coding a makefile, negating the savings in complexity

[openmediavault-official]

Who needs Portainer when you can have openmediavault-compose™?

[nixcraft]

Run a container inside another container! Linux nested virtualization lets you test complex setups, deploy apps easily, and even emulate AWS/GCP/Azure instances locally for fun and profit. See how to run Docker inside Incus containers

[qcs01]

Ansible Collections: Extending Ansible’s Capabilities

Ansible is a powerful automation tool used for configuration management, application deployment, and task automation. One of the key features that enhances its flexibility and extensibility is the concept of Ansible Collections. In this blog post, we'll explore what Ansible Collections are, how to create and use them, and look at some popular collections and their use cases.

Introduction to Ansible Collections

Ansible Collections are a way to package and distribute Ansible content. This content can include playbooks, roles, modules, plugins, and more. Collections allow users to organize their Ansible content and share it more easily, making it simpler to maintain and reuse.

Key Features of Ansible Collections:

Modularity: Collections break down Ansible content into modular components that can be independently developed, tested, and maintained.

Distribution: Collections can be distributed via Ansible Galaxy or private repositories, enabling easy sharing within teams or the wider Ansible community.

Versioning: Collections support versioning, allowing users to specify and depend on specific versions of a collection. How to Create and Use Collections in Your Projects

Creating and using Ansible Collections involves a few key steps. Here’s a guide to get you started:

1. Setting Up Your Collection

To create a new collection, you can use the ansible-galaxy command-line tool:

ansible-galaxy collection init my_namespace.my_collection

This command sets up a basic directory structure for your collection:

my_namespace/

└── my_collection/

├── docs/

├── plugins/

│ ├── modules/

│ ├── inventory/

│ └── ...

├── roles/

├── playbooks/

├── README.md

└── galaxy.yml

2. Adding Content to Your Collection

Populate your collection with the necessary content. For example, you can add roles, modules, and plugins under the respective directories. Update the galaxy.yml file with metadata about your collection.

3. Building and Publishing Your Collection

Once your collection is ready, you can build it using the following command:

ansible-galaxy collection build

This command creates a tarball of your collection, which you can then publish to Ansible Galaxy or a private repository:

ansible-galaxy collection publish my_namespace-my_collection-1.0.0.tar.gz

4. Using Collections in Your Projects

To use a collection in your Ansible project, specify it in your requirements.yml file:

collections:

- name: my_namespace.my_collection

version: 1.0.0

Then, install the collection using:

ansible-galaxy collection install -r requirements.yml

You can now use the content from the collection in your playbooks:--- - name: Example Playbook hosts: localhost tasks: - name: Use a module from the collection my_namespace.my_collection.my_module: param: value

Popular Collections and Their Use Cases

Here are some popular Ansible Collections and how they can be used:

1. community.general

Description: A collection of modules, plugins, and roles that are not tied to any specific provider or technology.

Use Cases: General-purpose tasks like file manipulation, network configuration, and user management.

2. amazon.aws

Description: Provides modules and plugins for managing AWS resources.

Use Cases: Automating AWS infrastructure, such as EC2 instances, S3 buckets, and RDS databases.

3. ansible.posix

Description: A collection of modules for managing POSIX systems.

Use Cases: Tasks specific to Unix-like systems, such as managing users, groups, and file systems.

4. cisco.ios

Description: Contains modules and plugins for automating Cisco IOS devices.

Use Cases: Network automation for Cisco routers and switches, including configuration management and backup.

5. kubernetes.core

Description: Provides modules for managing Kubernetes resources.

Use Cases: Deploying and managing Kubernetes applications, services, and configurations.

Conclusion

Ansible Collections significantly enhance the modularity, distribution, and reusability of Ansible content. By understanding how to create and use collections, you can streamline your automation workflows and share your work with others more effectively. Explore popular collections to leverage existing solutions and extend Ansible’s capabilities in your projects.

For more details click www.qcsdclabs.com

[telumiel]

I want to fucking strangle Docker, I love it but boy does it piss me off. The fuck you mean, do you really need more than 6GB ram